From: Wang Sheng-Hui <shhuiw-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org
Subject: [PATCH] madvise.2: update the description for MADV_REMOVE
Date: Wed, 25 Jun 2014 07:31:01 +0800 [thread overview]
Message-ID: <53AA0A35.9060100@gmail.com> (raw)
Currently we have more filesystems supporting fallcate, e.g ext4/btrfs,
which can response to MADV_REMOVE gracefully.
Update the MADV_REMOVE description.
Signed-off-by: Wang Sheng-Hui <shhuiw-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
man2/madvise.2 | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/man2/madvise.2 b/man2/madvise.2
index 032ead7..510530c 100644
--- a/man2/madvise.2
+++ b/man2/madvise.2
@@ -99,12 +99,8 @@ 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
+Free up a given range of pages and its associated backing store.
+Filesystems that don't support fallocate will return error
.BR ENOSYS .
.\" Databases want to use this feature to drop a section of their
.\" bufferpool (shared memory segments) - without writing back to
--
1.8.3.2
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-06-24 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 23:31 Wang Sheng-Hui [this message]
[not found] ` <53AA0A35.9060100-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-06-24 23:40 ` [PATCH] madvise.2: update the description for MADV_REMOVE Wang Sheng-Hui
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53AA0A35.9060100@gmail.com \
--to=shhuiw-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox