From: Mike Kravetz <mike.kravetz@oracle.com>
To: Alejandro Colomar <alx.manpages@gmail.com>,
linux-man@vger.kernel.org, linux-mm@kvack.org
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
David Hildenbrand <david@redhat.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH v3] madvise.2: Clarify addr/length and update hugetlb support
Date: Thu, 9 Jun 2022 11:48:06 -0700 [thread overview]
Message-ID: <3cf768b3-4d09-de13-7975-ebb74a68752e@oracle.com> (raw)
In-Reply-To: <a711288d-f070-e980-034a-3faee480e689@gmail.com>
On 6/9/22 06:24, Alejandro Colomar wrote:
> Hi Mike,
>
> On 6/9/22 01:45, 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>
>
> Please check some comments below.
>
> Thanks,
>
Thank you!
And, my apologies for not looking at formatting requirements.
Will send a v4 shortly.
--
Mike Kravetz
next prev parent reply other threads:[~2022-06-09 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 23:45 Mike Kravetz
2022-06-09 13:24 ` Alejandro Colomar
2022-06-09 18:48 ` Mike Kravetz [this message]
2022-06-09 20:13 ` Peter Xu
2022-06-10 9:01 ` David Hildenbrand
2022-06-10 9:38 ` Alejandro Colomar
2022-06-10 14:07 ` Peter Xu
2022-06-10 14:41 ` Alejandro Colomar
2022-08-15 20:41 ` Alejandro Colomar
2022-08-15 20:46 ` 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=3cf768b3-4d09-de13-7975-ebb74a68752e@oracle.com \
--to=mike.kravetz@oracle.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=mtk.manpages@gmail.com \
--cc=peterx@redhat.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