Currently we have more filesystems supporting fallcate, e.g ext4/btrfs, which can response to MADV_REMOVE gracefully. And if filesystems don't support fallocate, the return error would be EOPNOTSUPP, instead of ENOSYS. Signed-off-by: Wang Sheng-Hui <shhuiw@xxxxxxxxx> --- man2/madvise.2 | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/man2/madvise.2 b/man2/madvise.2 index 032ead7..4ce869c 100644 --- a/man2/madvise.2 +++ b/man2/madvise.2 @@ -99,13 +99,9 @@ or zero-fill-on-demand pages for mappings without an underlying file. .TP .BR MADV_REMOVE " (since Linux 2.6.16)" -Free up a given range of pages -and its associated backing store. -Currently, -.\" 2.6.18-rc5 -only shmfs/tmpfs supports this; other filesystems return with the -error -.BR ENOSYS . +Free up a given range of pages and its associated backing store. +Filesystems that don't support fallocate will return error +.BR EOPNOTSUPP. .\" Databases want to use this feature to drop a section of their .\" bufferpool (shared memory segments) - without writing back to .\" disk/swap space. This feature is also useful for supporting -- 1.8.3.2 -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
