summaryrefslogtreecommitdiffstats
path: root/mm/readahead.c
diff options
context:
space:
mode:
authorHugh Dickins2012-05-30 00:06:43 +0200
committerLinus Torvalds2012-05-30 01:22:23 +0200
commit4fb5ef089b288942c6fc3f85c4ecb4016c1aa4c3 (patch)
treeaff66acd4b8a0e8cc060f5bf20ad3d6d75bdb7ab /mm/readahead.c
parenttmpfs: quit when fallocate fills memory (diff)
downloadkernel-qcow2-linux-4fb5ef089b288942c6fc3f85c4ecb4016c1aa4c3.tar.gz
kernel-qcow2-linux-4fb5ef089b288942c6fc3f85c4ecb4016c1aa4c3.tar.xz
kernel-qcow2-linux-4fb5ef089b288942c6fc3f85c4ecb4016c1aa4c3.zip
tmpfs: support SEEK_DATA and SEEK_HOLE
It's quite easy for tmpfs to scan the radix_tree to support llseek's new SEEK_DATA and SEEK_HOLE options: so add them while the minutiae are still on my mind (in particular, the !PageUptodate-ness of pages fallocated but still unwritten). But I don't know who actually uses SEEK_DATA or SEEK_HOLE, and whether it would be of any use to them on tmpfs. This code adds 92 lines and 752 bytes on x86_64 - is that bloat or worthwhile? [akpm@linux-foundation.org: fix warning with CONFIG_TMPFS=n] Signed-off-by: Hugh Dickins <hughd@google.com> Cc: Christoph Hellwig <hch@infradead.org> Cc: Josef Bacik <josef@redhat.com> Cc: Andi Kleen <andi@firstfloor.org> Cc: Andreas Dilger <adilger@dilger.ca> Cc: Dave Chinner <david@fromorbit.com> Cc: Marco Stornelli <marco.stornelli@gmail.com> Cc: Jeff liu <jeff.liu@oracle.com> Cc: Chris Mason <chris.mason@oracle.com> Cc: Sunil Mushran <sunil.mushran@oracle.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/readahead.c')
0 files changed, 0 insertions, 0 deletions