From: John Hubbard <jhubbard@nvidia.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: David Hildenbrand <david@redhat.com>,
Jane Chu <jane.chu@oracle.com>,
linux-mm@kvack.org
Subject: Re: updated documentation: Splitting pinned folios
Date: Thu, 14 Mar 2024 10:57:29 -0700 [thread overview]
Message-ID: <19d7bca6-aa01-49a1-84f6-535b83d774d3@nvidia.com> (raw)
In-Reply-To: <ZfM31mgv1XYCeSbT@casper.infradead.org>
On 3/14/24 10:45, Matthew Wilcox wrote:
> On Wed, Mar 13, 2024 at 07:46:54PM -0700, John Hubbard wrote:
>> /*
>> * This function splits a huge page into normal pages. @page can point to any
>
> s/huge page/large folio/ and s/normal/smaller/ ?
OK. And yes, I did find that it's getting harder to figure out whether
to write "large folio" or "huge page" lately.
>
>> * subpage of the huge page to split. The split operation does not change the
>
> Trying to get away from "subpage", maybe "can point to any page within
> the folio"?
Sure, that works.
>
> I think following these suggestions throughout the text below will make
> it clearer ...
Will do. I'll post an actual patch against -rc1 with these and David's
corrections.
thanks,
--
John Hubbard
NVIDIA
prev parent reply other threads:[~2024-03-14 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 3:16 Matthew Wilcox
2024-03-13 9:20 ` David Hildenbrand
2024-03-13 15:27 ` Matthew Wilcox
2024-03-13 16:53 ` David Hildenbrand
2024-03-13 18:52 ` Jane Chu
2024-03-13 22:25 ` John Hubbard
2024-03-14 2:46 ` updated documentation: " John Hubbard
2024-03-14 16:22 ` David Hildenbrand
2024-03-14 17:51 ` John Hubbard
2024-03-14 17:45 ` Matthew Wilcox
2024-03-14 17:57 ` John Hubbard [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=19d7bca6-aa01-49a1-84f6-535b83d774d3@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=david@redhat.com \
--cc=jane.chu@oracle.com \
--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