linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Zach O'Keefe" <zokeefe@google.com>
To: Alex Colomar <alx.manpages@gmail.com>
Cc: Yang Shi <shy828301@gmail.com>,
	linux-mm@kvack.org, linux-man@vger.kernel.org
Subject: Re: [PATCH man-pages 1/4] madvise.2: update THP file/shmem documentation for +5.4
Date: Tue, 18 Oct 2022 09:52:05 -0700	[thread overview]
Message-ID: <CAAa6QmRQ10Q_C=6a7uOigsM8EBnonJ16JBmEDJWMB=tJ9AcU=A@mail.gmail.com> (raw)
In-Reply-To: <d748d5dd-d1ef-d421-25f3-1706e9ce1eea@gmail.com>

Hey Alex, thanks for taking a look!

> > diff --git a/man2/madvise.2 b/man2/madvise.2
> > index 81cce56af..e14e0f7fb 100644
> > --- a/man2/madvise.2
> > +++ b/man2/madvise.2
> > @@ -320,8 +320,6 @@ Enable Transparent Huge Pages (THP) for pages in the range specified by
> >   .I addr
> >   and
> >   .IR length .
> > -Currently, Transparent Huge Pages work only with private anonymous pages (see
> > -.BR mmap (2)).
> >   The kernel will regularly scan the areas marked as huge page candidates
> >   to replace them with huge pages.
> >   The kernel will also allocate huge pages directly when the region is
> > @@ -354,12 +352,45 @@ an access pattern that the developer knows in advance won't risk
> >   to increase the memory footprint of the application when transparent
> >   hugepages are enabled.
> >   .IP
> > +.\" commit 99cb0dbd47a15d395bf3faa78dc122bc5efe3fc0
> > +Since Linux 5.4,
> > +automatic scan of eligible areas and replacement by huge pages works with
> > +private anonymous pages (see
> > +.BR mmap (2)),
> > +shmem-backed pages (including tmpfs (see
> > +.BR tmpfs (5)),
>
> I think here's missing a closing parenthesis.  Please check.  Maybe you
> prefer combining em dashes or commas with parentheses to improve
> visually discerning subclauses.

Not only a good catch on the parenthesis, but I didn't actually know
about the "em dash" previously (though I'm a frequent user of it in
spirit). Thank you! With that in-hand, there are few places that could
be cleaned up to avoid nested paracentesis.

Best,
Zach


  reply	other threads:[~2022-10-18 16:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 17:55 [PATCH 0/4] Add MADV_COLLAPSE documentation Zach OKeefe
2022-10-17 17:55 ` [PATCH man-pages 1/4] madvise.2: update THP file/shmem documentation for +5.4 Zach OKeefe
2022-10-18 10:32   ` Alex Colomar
2022-10-18 16:52     ` Zach O'Keefe [this message]
2022-10-17 17:55 ` [PATCH man-pages 2/4] madvise.2: document reliable probe for advice support Zach OKeefe
2022-10-18 10:36   ` Alex Colomar
2022-10-18 17:53     ` Zach O'Keefe
2022-10-18 18:04       ` Alejandro Colomar
2022-10-18 18:30         ` Zach O'Keefe
2022-10-17 17:55 ` [PATCH man-pages 3/4] process_madvise.2: CAP_SYS_ADMIN cleanup Zach OKeefe
2022-10-18 10:38   ` Alex Colomar
2022-10-18 21:22     ` Zach O'Keefe
2022-10-17 17:55 ` [PATCH man-pages 4/4] madvise.2: add documentation for MADV_COLLAPSE Zach OKeefe
2022-10-18 10:47   ` Alex Colomar
2022-10-18 21:54     ` Zach O'Keefe

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='CAAa6QmRQ10Q_C=6a7uOigsM8EBnonJ16JBmEDJWMB=tJ9AcU=A@mail.gmail.com' \
    --to=zokeefe@google.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shy828301@gmail.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