From: Jiaqi Yan <jiaqiyan@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: tony.luck@intel.com, naoya.horiguchi@nec.com, duenwen@google.com,
rientjes@google.com, linux-mm@kvack.org, shy828301@gmail.com,
wangkefeng.wang@huawei.com
Subject: Re: [PATCH v1 0/3] Introduce per NUMA node memory error statistics
Date: Mon, 16 Jan 2023 13:52:08 -0800 [thread overview]
Message-ID: <CACw3F51dM6eSrkCRmzKjjFK0RmaXseFVAuMY_jkZRrq8Yi3JrQ@mail.gmail.com> (raw)
In-Reply-To: <20230116121305.a9412c9a54d086c83cbfc71f@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
On Mon, Jan 16, 2023 at 12:13 PM Andrew Morton <akpm@linux-foundation.org>
wrote:
> On Mon, 16 Jan 2023 19:38:59 +0000 Jiaqi Yan <jiaqiyan@google.com> wrote:
>
> > Background
> > ==========
> > In the RFC for Kernel Support of Memory Error Detection [1], one
> advantage
> > of software-based scanning over hardware patrol scrubber is the ability
> > to make statistics visible to system administrators. The statistics
> > include 2 categories:
> > * Memory error statistics, for example, how many memory error are
> > encountered, how many of them are recovered by the kernel. Note these
> > memory errors are non-fatal to kernel: during the machine check
> > exception (MCE) handling kernel already classified MCE's severity to
> > be unnecessary to panic (but either action required or optional).
> > * Scanner statistics, for example how many times the scanner have fully
> > scanned a NUMA node, how many errors are first detected by the scanner.
> >
> > The memory error statistics are useful to userspace and actually not
> > specific to scanner detected memory errors, and are the focus of this
> RFC.
>
> I assume this is a leftover and this is no longer "RFC".
>
> I'd normally sit back and await reviewer input, but this series is
> simple, so I'll slurp it up so we get some testing while that review is
> ongoing.
>
Ah, yes, my typo, my intent is PATCH.
I did test the patches on several test hosts I have, but more testing is
always better. Thanks, Andrew!
[-- Attachment #2: Type: text/html, Size: 2057 bytes --]
next prev parent reply other threads:[~2023-01-16 21:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 19:38 Jiaqi Yan
2023-01-16 19:39 ` [PATCH v1 1/3] mm: memory-failure: Add memory failure stats to sysfs Jiaqi Yan
2023-01-16 20:15 ` Andrew Morton
2023-01-17 9:14 ` HORIGUCHI NAOYA(堀口 直也)
2023-01-19 21:16 ` Jiaqi Yan
2023-01-17 9:02 ` HORIGUCHI NAOYA(堀口 直也)
2023-01-16 19:39 ` [PATCH v1 2/3] mm: memory-failure: Bump memory failure stats to pglist_data Jiaqi Yan
2023-01-16 20:16 ` Andrew Morton
2023-01-17 9:03 ` HORIGUCHI NAOYA(堀口 直也)
2023-01-18 23:05 ` Jiaqi Yan
2023-01-19 6:40 ` HORIGUCHI NAOYA(堀口 直也)
2023-01-19 18:05 ` Jiaqi Yan
2023-01-16 19:39 ` [PATCH v1 3/3] mm: memory-failure: Document memory failure stats Jiaqi Yan
2023-01-16 20:13 ` [PATCH v1 0/3] Introduce per NUMA node memory error statistics Andrew Morton
2023-01-16 21:52 ` Jiaqi Yan [this message]
2023-01-17 9:18 ` HORIGUCHI NAOYA(堀口 直也)
2023-01-17 17:51 ` Jiaqi Yan
2023-01-17 18:33 ` Luck, Tony
2023-01-18 17:31 ` Jiaqi Yan
2023-01-18 17:50 ` Luck, Tony
2023-01-18 23:33 ` Jiaqi Yan
2023-01-19 4:52 ` HORIGUCHI NAOYA(堀口 直也)
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=CACw3F51dM6eSrkCRmzKjjFK0RmaXseFVAuMY_jkZRrq8Yi3JrQ@mail.gmail.com \
--to=jiaqiyan@google.com \
--cc=akpm@linux-foundation.org \
--cc=duenwen@google.com \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=rientjes@google.com \
--cc=shy828301@gmail.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