From: SeongJae Park <sj@kernel.org>
To: Jiaqi Yan <jiaqiyan@google.com>
Cc: SeongJae Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-doc@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the mm tree
Date: Tue, 2 Jul 2024 16:09:51 -0700 [thread overview]
Message-ID: <20240702230951.78721-1-sj@kernel.org> (raw)
In-Reply-To: <CACw3F52_obAB742XeDRNun4BHBYtrxtbvp5NkUincXdaob0j1g@mail.gmail.com>
Hello Jiaqi,
On Mon, 1 Jul 2024 23:37:55 -0700 Jiaqi Yan <jiaqiyan@google.com> wrote:
> On Mon, Jul 1, 2024 at 11:18 PM Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > On Mon, 1 Jul 2024 21:33:20 -0700 Jiaqi Yan <jiaqiyan@google.com> wrote:
> >
> > > > > This seems a reasonable thing to do so there's probably some way in
> > > > > which to do it, but a bit of grepping failed to turn up examples in
> > > > > existing .rst files. Can someone please suggest?
> > > >
> > > > It seems I need to add some blank lines according to [1], especially
> > > > to add a blank line above the first list item:
According to my understanding and testing on my machine, it seems we need blank
lines only before and after the blocks.
[...]
>
> Ah, sorry Andrew, I should sent out this diff, as there are more blank
> lines needed:
>
> diff --git a/Documentation/admin-guide/sysctl/vm.rst
> b/Documentation/admin-guide/sysctl/vm.rst
> index 75e22137d849..f48eaa98d22d 100644
> --- a/Documentation/admin-guide/sysctl/vm.rst
> +++ b/Documentation/admin-guide/sysctl/vm.rst
> @@ -274,12 +274,15 @@ Correctable memory errors are very common on
> servers. Soft-offline is kernel's
> solution for memory pages having (excessive) corrected memory errors.
>
> For different types of page, soft-offline has different behaviors / costs.
> +
So, this was needed to make 'make htmldocs' quiet on my machine.
> - For a raw error page, soft-offline migrates the in-use page's content to
> a new raw page.
> +
> - For a page that is part of a transparent hugepage, soft-offline splits the
> transparent hugepage into raw pages, then migrates only the raw error page.
> As a result, user is transparently backed by 1 less hugepage, impacting
> memory access performance.
> +
But above two blank lines were not really needed to make 'make htmldocs' calm,
at least on my setup. Many other documents also don't have this kind of blank
line.
> - For a page that is part of a HugeTLB hugepage, soft-offline first migrates
> the entire HugeTLB hugepage, during which a free hugepage will be consumed
> as migration target. Then the original hugepage is dissolved into raw
> @@ -296,8 +299,11 @@ the request to soft offline the pages. Its
> default value is 1.
>
> It is worth mentioning that after setting enable_soft_offline to 0, the
> following requests to soft offline pages will not be performed:
> +
Interestingly, 'make htmldocs' didn't complain even if I don't put this blank
line. But for consistency (see the beginning of sysctl/vm.rst), I think having
this would be good.
> - Request to soft offline pages from RAS Correctable Errors Collector.
> +
> - On ARM, the request to soft offline pages from GHES driver.
> +
Again, same to the reason above, it seems above two blank lines are not really
needed.
> - On PARISC, the request to soft offline pages from Page Deallocation Table.
>
> extfrag_threshold
>
I have no strong opinion about these, though. Having four more blank lines
that might unnecessary is obviously no problem.
Thanks,
SJ
next prev parent reply other threads:[~2024-07-02 23:09 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-01 8:49 linux-next: build warnings after merge of the mm tree Stephen Rothwell
2024-07-02 3:14 ` Andrew Morton
2024-07-02 4:15 ` Jiaqi Yan
2024-07-02 4:33 ` Jiaqi Yan
2024-07-02 6:18 ` Andrew Morton
2024-07-02 6:37 ` Jiaqi Yan
2024-07-02 23:09 ` SeongJae Park [this message]
2024-07-02 23:55 ` Jiaqi Yan
-- strict thread matches above, loose matches on Subject: below --
2025-03-05 9:42 Stephen Rothwell
2025-03-05 9:53 ` David Hildenbrand
2025-03-05 10:05 ` David Hildenbrand
2025-02-17 6:10 Stephen Rothwell
2025-02-17 16:28 ` Suren Baghdasaryan
2025-02-10 3:49 Stephen Rothwell
2025-02-09 23:06 Stephen Rothwell
2025-01-06 6:42 Stephen Rothwell
2024-09-11 10:21 Stephen Rothwell
2024-07-01 1:01 Stephen Rothwell
2024-07-01 1:13 ` Andrii Nakryiko
2024-07-01 8:28 ` Stephen Rothwell
2024-03-25 1:36 Stephen Rothwell
2024-03-26 2:19 ` Suren Baghdasaryan
2024-03-26 5:44 ` Randy Dunlap
2024-03-26 6:16 ` Suren Baghdasaryan
2024-03-28 4:39 ` Stephen Rothwell
2024-03-28 4:44 ` Stephen Rothwell
2024-03-28 5:35 ` Suren Baghdasaryan
2024-03-29 22:49 ` Stephen Rothwell
2024-03-29 23:01 ` Suren Baghdasaryan
2024-03-29 23:01 ` Suren Baghdasaryan
2024-02-21 5:27 Stephen Rothwell
2024-02-21 17:12 ` SeongJae Park
2023-07-27 4:28 Stephen Rothwell
2023-07-27 4:46 ` Aneesh Kumar K.V
2023-07-27 5:00 ` Stephen Rothwell
2023-05-08 4:54 Stephen Rothwell
2023-05-08 16:10 ` Liam R. Howlett
2022-11-22 6:50 Stephen Rothwell
2022-08-23 3:54 Stephen Rothwell
2022-08-23 14:55 ` Liam Howlett
2022-05-11 10:20 Stephen Rothwell
2022-05-11 16:06 ` Johannes Weiner
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=20240702230951.78721-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jiaqiyan@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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