From: Mike Rapoport <rppt@linux.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs/vm: add documentation of memory models
Date: Thu, 25 Apr 2019 11:22:40 +0300 [thread overview]
Message-ID: <20190425082239.GC10625@rapoport-lnx> (raw)
In-Reply-To: <a4def881-1df0-6835-4b9a-dc957c979683@infradead.org>
Hi Randy,
On Wed, Apr 24, 2019 at 06:08:46PM -0700, Randy Dunlap wrote:
> On 4/24/19 3:28 AM, Mike Rapoport wrote:
> > Describe what {FLAT,DISCONTIG,SPARSE}MEM are and how they manage to
> > maintain pfn <-> struct page correspondence.
> >
> > Signed-off-by: Mike Rapoport <rppt@linux.ibm.com>
> > ---
> > Documentation/vm/index.rst | 1 +
> > Documentation/vm/memory-model.rst | 171 ++++++++++++++++++++++++++++++++++++++
> > 2 files changed, 172 insertions(+)
> > create mode 100644 Documentation/vm/memory-model.rst
> >
>
> Hi Mike,
> I have a few minor edits below...
I kinda expected those ;-)
> > diff --git a/Documentation/vm/memory-model.rst b/Documentation/vm/memory-model.rst
> > new file mode 100644
> > index 0000000..914c52a
> > --- /dev/null
> > +++ b/Documentation/vm/memory-model.rst
...
> > +
> > +With FLATMEM, the conversion between a PFN and the `struct page` is
> > +straightforward: `PFN - ARCH_PFN_OFFSET` is an index to the
> > +`mem_map` array.
> > +
> > +The `ARCH_PFN_OFFSET` defines the first page frame number for
> > +systems that their physical memory does not start at 0.
>
> s/that/when/ ? Seems awkward as is.
Yeah, it is awkward. How about
The `ARCH_PFN_OFFSET` defines the first page frame number for
systems with physical memory starting at address different from 0.
> > +
> > +DISCONTIGMEM
> > +============
> > +
>
> thanks.
> --
> ~Randy
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2019-04-25 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 10:28 Mike Rapoport
2019-04-24 10:50 ` Anshuman Khandual
2019-04-24 11:35 ` Mike Rapoport
2019-04-24 16:14 ` Jonathan Corbet
2019-04-24 18:02 ` Mike Rapoport
2019-04-25 1:08 ` Randy Dunlap
2019-04-25 8:22 ` Mike Rapoport [this message]
2019-04-25 15:01 ` Randy Dunlap
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=20190425082239.GC10625@rapoport-lnx \
--to=rppt@linux.ibm.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@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