From: Miaohe Lin <linmiaohe@huawei.com>
To: Jiaqi Yan <jiaqiyan@google.com>
Cc: <muchun.song@linux.dev>, <akpm@linux-foundation.org>,
<shuah@kernel.org>, <corbet@lwn.net>, <osalvador@suse.de>,
<rientjes@google.com>, <duenwen@google.com>, <fvdl@google.com>,
<linux-mm@kvack.org>, <linux-kselftest@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <nao.horiguchi@gmail.com>,
<jane.chu@oracle.com>, <ioworker0@gmail.com>
Subject: Re: [PATCH v5 4/4] docs: mm: add enable_soft_offline sysctl
Date: Tue, 25 Jun 2024 15:16:28 +0800 [thread overview]
Message-ID: <b9be3eff-6f69-5286-0dd9-30e562bdb7d2@huawei.com> (raw)
In-Reply-To: <20240624163348.1751454-5-jiaqiyan@google.com>
On 2024/6/25 0:33, Jiaqi Yan wrote:
> Add the documentation for soft offline behaviors / costs, and what
> the new enable_soft_offline sysctl is for.
>
> Acked-by: Oscar Salvador <osalvador@suse.de>
>
> Signed-off-by: Jiaqi Yan <jiaqiyan@google.com>
> ---
> Documentation/admin-guide/sysctl/vm.rst | 32 +++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
LGTM. Thanks.
Acked-by: Miaohe Lin <linmiaohe@huawei.com>
Thanks.
.
next prev parent reply other threads:[~2024-06-25 7:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 16:33 [PATCH v5 0/4] Userspace controls soft-offline pages Jiaqi Yan
2024-06-24 16:33 ` [PATCH v5 1/4] mm/memory-failure: refactor log format in soft offline code Jiaqi Yan
2024-06-25 6:40 ` Miaohe Lin
2024-06-25 15:48 ` Jiaqi Yan
2024-06-24 16:33 ` [PATCH v5 2/4] mm/memory-failure: userspace controls soft-offlining pages Jiaqi Yan
2024-06-24 16:33 ` [PATCH v5 3/4] selftest/mm: test enable_soft_offline behaviors Jiaqi Yan
2024-06-25 7:05 ` Miaohe Lin
[not found] ` <CACw3F51yApRGaKcKmeEo-SYbt-nxULCwe2imCnsaPP8m4UBW6g@mail.gmail.com>
2024-06-26 1:54 ` Miaohe Lin
2024-06-26 3:57 ` Jiaqi Yan
2024-06-24 16:33 ` [PATCH v5 4/4] docs: mm: add enable_soft_offline sysctl Jiaqi Yan
2024-06-25 7:16 ` Miaohe Lin [this message]
2024-06-26 0:02 ` Randy Dunlap
2024-06-26 0:18 ` Jiaqi Yan
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=b9be3eff-6f69-5286-0dd9-30e562bdb7d2@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=duenwen@google.com \
--cc=fvdl@google.com \
--cc=ioworker0@gmail.com \
--cc=jane.chu@oracle.com \
--cc=jiaqiyan@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=rientjes@google.com \
--cc=shuah@kernel.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