From: David Rientjes <rientjes@google.com>
To: Wang Sheng-Hui <shhuiw@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Andi Kleen <ak@linux.intel.com>,
Vladimir Cernov <gg.kaspersky@gmail.com>,
linux-mm@kvack.org, linux-api@vger.kernel.org,
linux-man@vger.kernel.org
Subject: Re: [PATCH] mm: update the description for madvise_remove
Date: Wed, 25 Jun 2014 15:30:31 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1406251529530.4592@chino.kir.corp.google.com> (raw)
In-Reply-To: <53AA2CD5.6060202@gmail.com>
On Wed, 25 Jun 2014, Wang Sheng-Hui wrote:
> Patch to man-page.
>
> [PATCH] madvise.2: update the description for MADV_REMOVE
>
> 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@gmail.com>
Great, thanks! This looks like it can be applied immediately and doesn't
require us to wait for any kernel change.
Good catch with the return value.
> ---
> 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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-06-25 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 5:49 Wang Sheng-Hui
2014-06-24 5:59 ` Naoya Horiguchi
2014-06-24 22:44 ` David Rientjes
2014-06-25 1:58 ` Wang Sheng-Hui
2014-06-25 22:30 ` David Rientjes [this message]
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=alpine.DEB.2.02.1406251529530.4592@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=gg.kaspersky@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=shhuiw@gmail.com \
/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