From: Zi Yan <ziy@nvidia.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, David Hildenbrand <david@redhat.com>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] huge_memory.c: document huge page splitting rules more thoroughly
Date: Mon, 25 Mar 2024 09:28:17 -0400 [thread overview]
Message-ID: <B9A3BBFA-5DE2-4C72-9CB0-38086001577F@nvidia.com> (raw)
In-Reply-To: <20240325044452.217463-1-jhubbard@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
On 25 Mar 2024, at 0:44, John Hubbard wrote:
> 1. Add information about the behavior of huge page splitting, with
> respect to page/folio refcounts, and gup/pup pins.
>
> 2. Update and clarify the existing documentation, to compensate for the
> ravages of time and code change.
>
> Cc: David Hildenbrand <david@redhat.com>
> Cc: Matthew Wilcox <willy@infradead.org>
> Cc: Zi Yan <ziy@nvidia.com>
>
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
> ---
>
> Hi David, Matthew, Zi,
>
> This is a follow up from our short email thread of a week ago [1].
>
> Zi, I've inflicted some minor violence upon your original wording, and
> moved it into a Prerequisites section (item 4).
>
>
> [1] https://lore.kernel.org/all/d9c06bec-805f-4d53-9f91-6b8ad29fcb6b@redhat.com/
>
> thanks,
> John Hubbard
> NVIDIA
>
> mm/huge_memory.c | 42 +++++++++++++++++++++++++++---------------
> 1 file changed, 27 insertions(+), 15 deletions(-)
>
LGTM. Thanks. Reviewed-by: Zi Yan <ziy@nvidia.com>
--
Best Regards,
Yan, Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next prev parent reply other threads:[~2024-03-25 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 4:44 John Hubbard
2024-03-25 13:28 ` Zi Yan [this message]
2024-03-25 14:05 ` David Hildenbrand
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=B9A3BBFA-5DE2-4C72-9CB0-38086001577F@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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