From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jiaqi Yan <jiaqiyan@google.com>,
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: Mon, 1 Jul 2024 20:14:48 -0700 [thread overview]
Message-ID: <20240701201448.7878e9b35e1569bfc1f2ddbc@linux-foundation.org> (raw)
In-Reply-To: <20240701184912.01f1f9ce@canb.auug.org.au>
On Mon, 1 Jul 2024 18:49:12 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the mm tree, today's linux-next build (htmldocs) produced
> these warnings:
>
> Documentation/admin-guide/sysctl/vm.rst:278: ERROR: Unexpected indentation.
> Documentation/admin-guide/sysctl/vm.rst:279: WARNING: Block quote ends without a blank line; unexpected unindent.
>
> Introduced by commit
>
> 2cba7831f62c ("docs: mm: add enable_soft_offline sysctl")
Well that's annoying.
@@ -267,6 +268,37 @@ used::
These are informational only. They do not mean that anything is wrong
with your system. To disable them, echo 4 (bit 2) into drop_caches.
+enable_soft_offline
+===================
+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.
+- 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.
+- 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
+ pages without compensation, reducing the capacity of the HugeTLB pool by 1.
+
+ ...
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?
next prev parent reply other threads:[~2024-07-02 3:14 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 [this message]
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
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=20240701201448.7878e9b35e1569bfc1f2ddbc@linux-foundation.org \
--to=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