diff options
author | Andrew Morton <akpm@osdl.org> | 2006-08-05 12:14:25 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-08-06 08:57:47 -0700 |
commit | 60c371bc753495f36d3a71338b46030f7fffce3b (patch) | |
tree | ec83d5b3cc89efcea66310f3a1c6ca3708f6a26e /include/linux/debug_locks.h | |
parent | bb39e419740435b7fbb0314e376ba468be7db67a (diff) | |
download | kernel_samsung_smdk4412-60c371bc753495f36d3a71338b46030f7fffce3b.zip kernel_samsung_smdk4412-60c371bc753495f36d3a71338b46030f7fffce3b.tar.gz kernel_samsung_smdk4412-60c371bc753495f36d3a71338b46030f7fffce3b.tar.bz2 |
[PATCH] fadvise() make POSIX_FADV_NOREUSE a no-op
The POSIX_FADV_NOREUSE hint means "the application will use this range of the
file a single time". It seems to be intended that the implementation will use
this hint to perform drop-behind of that part of the file when the application
gets around to reading or writing it.
However for reasons which aren't obvious (or sane?) I mapped
POSIX_FADV_NOREUSE onto POSIX_FADV_WILLNEED. ie: it does readahead.
That's daft. So for now, make POSIX_FADV_NOREUSE a no-op.
This is a non-back-compatible change. If someone was using POSIX_FADV_NOREUSE
to perform readahead, they lose. The likelihood is low.
If/when we later implement POSIX_FADV_NOREUSE things will get interesting - to
do it fully we'll need to maintain file offset/length ranges and peform all
sorts of complex tricks, and managing the lifetime of those ranges' data
structures will be interesting..
A sensible implementation would probably ignore the file range and would
simply mark the entire file as needing some form of drop-behind treatment.
Cc: Michael Kerrisk <mtk-manpages@gmx.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'include/linux/debug_locks.h')
0 files changed, 0 insertions, 0 deletions