From: "HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>
To: wangbin <wangbin224@huawei.com>
Cc: "mike.kravetz@oracle.com" <mike.kravetz@oracle.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"nao.horiguchi@gmail.com" <nao.horiguchi@gmail.com>,
"wuxu.wu@huawei.com" <wuxu.wu@huawei.com>
Subject: Re: Re: [PATCH] mm: hugetlbfs: add hwcrp_hugepages to record memory failure on hugetlbfs
Date: Tue, 8 Jun 2021 09:13:52 +0000 [thread overview]
Message-ID: <20210608091352.GA943097@hori.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <20210608022450.2044-1-wangbin224@huawei.com>
On Tue, Jun 08, 2021 at 10:24:50AM +0800, wangbin wrote:
> > What specific problem are you trying to solve? Are trying to see how
> > many huge pages were hit by memory errors?
>
> Yes, I'd like to know how many huge pages are not available because of
> the memory errors. Just like HardwareCorrupted in the /proc/meminfo.
> But the HardwareCorrupted only adds one page size when a huge page is
> hit by memory errors, and mixes with normal pages. So I think we should
> add a new counts to track the memory errors on hugetlbfs.
If you can use root privilege in your use-case, an easy way to get the
number of corrupted hugepages is to use page-types.c (which reads
/proc/kpageflags) like below:
$ page-types -b huge,hwpoison=huge,hwpoison
flags page-count MB symbolic-flags long-symbolic-flags
0x00000000000a8000 1 0 _______________H_G_X_______________________ compound_head,huge,hwpoison
total 1 0
But I guess that many usecases do not permit access to this interface,
where some new accounting interface for corrupted hugepages could be
helpful as you suggest.
Thanks,
Naoya Horiguchi
next prev parent reply other threads:[~2021-06-08 9:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 14:16 wangbin
2021-06-07 19:07 ` Mike Kravetz
2021-06-07 19:13 ` Mike Kravetz
2021-06-08 2:24 ` wangbin
2021-06-08 9:13 ` HORIGUCHI NAOYA(堀口 直也) [this message]
2021-06-09 2:23 ` wangbin
2021-06-08 8:01 ` 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=20210608091352.GA943097@hori.linux.bs1.fc.nec.co.jp \
--to=naoya.horiguchi@nec.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=nao.horiguchi@gmail.com \
--cc=wangbin224@huawei.com \
--cc=wuxu.wu@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
all inboxes | Powered by JetHome®