linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Tomohiro Misono (Fujitsu)" <misono.tomohiro@fujitsu.com>
To: "'jane.chu@oracle.com'" <jane.chu@oracle.com>,
	'Miaohe Lin' <linmiaohe@huawei.com>,
	'Jiaqi Yan' <jiaqiyan@google.com>
Cc: "'linux-mm@kvack.org'" <linux-mm@kvack.org>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	'Andrew Morton' <akpm@linux-foundation.org>,
	'Naoya Horiguchi' <nao.horiguchi@gmail.com>
Subject: RE: [RFC PATCH] mm: memory-failure: add soft-offline stat in mf_stats
Date: Tue, 10 Dec 2024 08:46:20 +0000	[thread overview]
Message-ID: <TYCPR01MB96175844C1C9DD89BC16675EE53D2@TYCPR01MB9617.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <83a8698a-fe11-42e2-8a4b-ea236721f93f@oracle.com>

> >>> And
> >>> 1. total = recovered + ignored + failed + delayed
> >>> 2. recovered = soft_offline + hard_offline
> >> Do you mean mf_stats now have 7 entries in sysfs?
> >> (total, ignored, failed, delayed, recovered, hard_offline, soft_offline, then recovered = hard_offline +
> soft_offline)
> >> Or 6 entries ? (in that case, hard_offline = recovered - soft_offline)
> >> It might be simpler to understand for user if total is just the sum of other entries like this RFC,
> >> but I'd like to know other opinions.
> > Will it be better to have below items?
> > "
> > total
> > ignored
> > failed
> > dalayed
> > hard_offline
> > soft_offline
> > "
> 
> The existing "ignored, failed, delayed, recovered" apply to UEs while
> "soft_offline" applies to CE. The difference between UE and CE is that
> even a recovered UE page has PG_hwpoison set, but a soft offlined page
> does not and thus could be re-deployed.

Hi, thanks for your comments.

If I understand correctly, PG_hwpoison is also set in soft offlined page (and thus
counted in HardwareCorrupted too):
  https://github.com/torvalds/linux/blob/v6.13-rc2/mm/memory-failure.c#L206
Also, unpoison works but can only be used via debugfs by hwpoison-inject module.
Is this correct?

> 
> So if we want to flag CE pages, they seem to belong to a different
> category, something like -
> 
> /sys/devices/system/node/node0/memory_failure/Uncorrected/{ignored, delayed, failed, recovered}
> /sys/devices/system/node/node0/memory_failure/Corrected/{offlined}

This makes sense. But as I stated in other thread, I don't think we can change the
current I/F for "Uncorrected". Is it worth to create "Corrected" dir only?

Regards
Tomohiro Misono

      reply	other threads:[~2024-12-10  8:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21  4:55 Tomohiro Misono
2024-11-26  3:09 ` Miaohe Lin
2024-11-27  2:32   ` Tomohiro Misono (Fujitsu)
2024-11-27  7:06     ` Jiaqi Yan
2024-11-28  5:46       ` Tomohiro Misono (Fujitsu)
2024-11-29  7:07         ` Miaohe Lin
2024-11-29  8:26           ` Tomohiro Misono (Fujitsu)
2024-11-29  9:07             ` Miaohe Lin
2024-12-07  0:17           ` jane.chu
2024-12-10  8:46             ` Tomohiro Misono (Fujitsu) [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=TYCPR01MB96175844C1C9DD89BC16675EE53D2@TYCPR01MB9617.jpnprd01.prod.outlook.com \
    --to=misono.tomohiro@fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=jane.chu@oracle.com \
    --cc=jiaqiyan@google.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nao.horiguchi@gmail.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