From: Peter Xu <peterx@redhat.com>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: linux-man@vger.kernel.org, linux-mm@kvack.org,
Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
David Hildenbrand <david@redhat.com>,
Axel Rasmussen <axelrasmussen@google.com>
Subject: Re: [PATCH v2] madvise.2: Clarify addr/length and update hugetlb support
Date: Thu, 26 May 2022 14:21:17 -0400 [thread overview]
Message-ID: <Yo/FHRV+i1VNf+o2@xz-m1.local> (raw)
In-Reply-To: <20220526180950.13916-1-mike.kravetz@oracle.com>
On Thu, May 26, 2022 at 11:09:50AM -0700, Mike Kravetz wrote:
> Clarify that madvise only works on full pages, and remove references
> to 'bytes'.
>
> Update MADV_DONTNEED and MADV_REMOVE sections to remove notes that
> HugeTLB mappings are not supported. Indicate the releases when they
> were first supported as well as alignment restrictions.
>
> Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
Acked-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2022-05-26 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 18:09 [PATCH v2] madvise.2: Clarify addr/length and update hugetlb support Mike Kravetz
2022-05-26 18:21 ` Peter Xu [this message]
2022-05-31 9:10 ` David Hildenbrand
2022-06-03 17:02 ` man-pages maintainership (was: Re: [PATCH v2] madvise.2: Clarify addr/length and update hugetlb support) Alejandro Colomar
2022-06-03 17:42 ` Alejandro Colomar
2022-06-07 7:44 ` David Hildenbrand
2022-06-07 9:37 ` Alejandro Colomar
2022-06-08 10:00 ` David Hildenbrand
2022-06-08 11:41 ` Alejandro Colomar
2022-06-06 19:12 ` [PATCH v2] madvise.2: Clarify addr/length and update hugetlb support Alejandro Colomar
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=Yo/FHRV+i1VNf+o2@xz-m1.local \
--to=peterx@redhat.com \
--cc=alx.manpages@gmail.com \
--cc=axelrasmussen@google.com \
--cc=david@redhat.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=mtk.manpages@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;
as well as URLs for NNTP newsgroup(s).