From: Andrew Morton <akpm@linux-foundation.org>
To: Jiaqi Yan <jiaqiyan@google.com>
Cc: kirill.shutemov@linux.intel.com, kirill@shutemov.name,
shy828301@gmail.com, tongtiangen@huawei.com, tony.luck@intel.com,
wangkefeng.wang@huawei.com, naoya.horiguchi@nec.com,
linmiaohe@huawei.com, linux-mm@kvack.org, osalvador@suse.de
Subject: Re: [PATCH v9 0/2] Memory poison recovery in khugepaged collapsing
Date: Wed, 18 Jan 2023 15:29:20 -0800 [thread overview]
Message-ID: <20230118152920.570334ca836e84a0dbf870be@linux-foundation.org> (raw)
In-Reply-To: <20221205234059.42971-1-jiaqiyan@google.com>
On Mon, 5 Dec 2022 15:40:57 -0800 Jiaqi Yan <jiaqiyan@google.com> wrote:
> Problem
> =======
> Memory DIMMs are subject to multi-bit flips, i.e. memory errors.
> As memory size and density increase, the chances of and number of
> memory errors increase. The increasing size and density of server
> RAM in the data center and cloud have shown increased uncorrectable
> memory errors. There are already mechanisms in the kernel to recover
> from uncorrectable memory errors. This series of patches provides
> the recovery mechanism for the particular kernel agent khugepaged
> when it collapses memory pages.
Could we please have some reviewer input on this series?
Thanks.
prev parent reply other threads:[~2023-01-18 23:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 23:40 Jiaqi Yan
2022-12-05 23:40 ` [PATCH v9 1/2] mm/khugepaged: recover from poisoned anonymous memory Jiaqi Yan
2023-01-19 15:02 ` kirill.shutemov
2023-01-20 15:56 ` Jiaqi Yan
2023-01-24 0:33 ` kirill.shutemov
2023-02-01 5:16 ` Jiaqi Yan
2023-02-02 0:01 ` kirill.shutemov
2023-02-02 0:30 ` kirill
2023-02-07 18:19 ` Jiaqi Yan
2023-02-08 11:44 ` Alexander Potapenko
2023-02-08 23:00 ` Jiaqi Yan
2023-02-17 19:49 ` Jiaqi Yan
2023-02-28 13:40 ` kirill
2023-03-03 17:15 ` Jiaqi Yan
2022-12-05 23:40 ` [PATCH v9 2/2] mm/khugepaged: recover from poisoned file-backed memory Jiaqi Yan
2023-01-19 15:10 ` kirill.shutemov
2023-01-19 21:24 ` Jiaqi Yan
2023-01-18 23:29 ` Andrew Morton [this message]
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=20230118152920.570334ca836e84a0dbf870be@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jiaqiyan@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=tongtiangen@huawei.com \
--cc=tony.luck@intel.com \
--cc=wangkefeng.wang@huawei.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