From: David Hildenbrand <david@redhat.com>
To: John Hubbard <jhubbard@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Matthew Wilcox <willy@infradead.org>,
Zi Yan <ziy@nvidia.com>
Subject: Re: [PATCH] huge_memory.c: document huge page splitting rules more thoroughly
Date: Mon, 25 Mar 2024 15:05:00 +0100 [thread overview]
Message-ID: <30e9e4da-334e-4e48-a716-5edc2f2c0c21@redhat.com> (raw)
In-Reply-To: <20240325044452.217463-1-jhubbard@nvidia.com>
On 25.03.24 05: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>
> ---
Thanks!
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-03-25 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 4:44 [PATCH] huge_memory.c: document huge page splitting rules more thoroughly John Hubbard
2024-03-25 13:28 ` Zi Yan
2024-03-25 14:05 ` David Hildenbrand [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=30e9e4da-334e-4e48-a716-5edc2f2c0c21@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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).