From: Jan Chaloupka <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
hughd-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH] madvise.2: madvise(, , MADV_REMOVE) supports ext4, ocfs2 and xfs as well
Date: Mon, 13 Oct 2014 10:24:16 +0200 [thread overview]
Message-ID: <543B8C30.2070007@redhat.com> (raw)
In-Reply-To: <20141007140337.10571.62743.stgit-/v0jm+aXwyk2pP1PFFXgSPXAX3CI6PSWQQ4Iyu8u01E@public.gmane.org>
ping
On 10/07/2014 04:03 PM, Jan Chaloupka wrote:
> As from upstream commit:
>
> commit 3f31d07571eeea18a7d34db9af21d2285b807a17
> Author: Hugh Dickins <hughd-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
> Date: Tue May 29 15:06:40 2012 -0700
>
> mm/fs: route MADV_REMOVE to FALLOC_FL_PUNCH_HOLE
>
> Now tmpfs supports hole-punching via fallocate(), switch madvise_remove()
> to use do_fallocate() instead of vmtruncate_range(): which extends
> madvise(,,MADV_REMOVE) support from tmpfs to ext4, ocfs2 and xfs.
>
> madvise(,,MADV_REMOVE) support was extended by ext4, ocfs2 and xfs.
>
> bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1120294
>
> Justification from Rafael Aquini:
> Well, that code is committed in kernel since v3.5 (2012) and it surely is
> the expected behaviour since. It seems to me that madvise(2) man page text
> for MADV_REMOVE just got out-of-date in that regard.
>
> This patch mentions this support in madvise.2 man page.
>
> Signed-off-by: Jan Chaloupka <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
> man2/madvise.2 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man2/madvise.2 b/man2/madvise.2
> index 032ead7..44698ec 100644
> --- a/man2/madvise.2
> +++ b/man2/madvise.2
> @@ -98,12 +98,12 @@ either in reloading of the memory contents from the underlying mapped file
> or zero-fill-on-demand pages for mappings
> without an underlying file.
> .TP
> -.BR MADV_REMOVE " (since Linux 2.6.16)"
> +.BR MADV_REMOVE " (since Linux 3.5)"
> 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
> +only shmfs/tmpfs, ext4, ocfs2 and xfs supports this; other filesystems return with the
> error
> .BR ENOSYS .
> .\" Databases want to use this feature to drop a section of their
>
--
Jan Chaloupka
------------------------------
* Software Engineer *
* ENG Base Operating Systems *
* Red Hat Czech, s. r. o. *
* UTC+1 (CET), jchaloup *
--
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 prev parent reply other threads:[~2014-10-13 8:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 14:03 [PATCH] madvise.2: madvise(, , MADV_REMOVE) supports ext4, ocfs2 and xfs as well Jan Chaloupka
[not found] ` <20141007140337.10571.62743.stgit-/v0jm+aXwyk2pP1PFFXgSPXAX3CI6PSWQQ4Iyu8u01E@public.gmane.org>
2014-10-13 8:24 ` Jan Chaloupka [this message]
2014-10-16 10:50 ` Jan Chaloupka
2014-10-17 14:35 ` Michael Kerrisk (man-pages)
[not found] ` <5441292E.5000008-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-10-17 21:52 ` Hugh Dickins
[not found] ` <alpine.LSU.2.11.1410171408260.11102-fupSdm12i1nKWymIFiNcPA@public.gmane.org>
2014-10-18 15:11 ` Jan Chaloupka
-- strict thread matches above, loose matches on Subject: below --
2014-10-18 15:22 Jan Chaloupka
[not found] ` <20141018152240.14951.14405.stgit-/v0jm+aXwyk2pP1PFFXgSPXAX3CI6PSWQQ4Iyu8u01E@public.gmane.org>
2014-10-22 8:41 ` Jan Chaloupka
2015-02-04 9:28 ` Michael Kerrisk (man-pages)
[not found] ` <CAKgNAkg_cOKFC_Mjmn+EjLr4PDnb2GKRq7BhKaEpdks9tgSa9A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-02-04 9:39 ` Jan Chaloupka
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=543B8C30.2070007@redhat.com \
--to=jchaloup-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=hughd-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).