From: jane.chu@oracle.com
To: "Luck, Tony" <tony.luck@intel.com>, Jiaqi Yan <jiaqiyan@google.com>
Cc: "nao.horiguchi@gmail.com" <nao.horiguchi@gmail.com>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"wangkefeng.wang@huawei.com" <wangkefeng.wang@huawei.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"osalvador@suse.de" <osalvador@suse.de>,
"rientjes@google.com" <rientjes@google.com>,
"duenwen@google.com" <duenwen@google.com>,
"jthoughton@google.com" <jthoughton@google.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"ankita@nvidia.com" <ankita@nvidia.com>,
"peterx@redhat.com" <peterx@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [RFC PATCH v1 1/2] mm/memory-failure: introduce global MFR policy
Date: Tue, 15 Oct 2024 17:19:49 -0700 [thread overview]
Message-ID: <5720bfe9-fb81-49e4-adb4-7b017cf759bb@oracle.com> (raw)
In-Reply-To: <SJ1PR11MB6083829F88D5102E94FD80A0FC452@SJ1PR11MB6083.namprd11.prod.outlook.com>
On 10/15/2024 4:56 PM, Luck, Tony wrote:
>> Another way to "disable hardoffline but still set HWPoison" I can
>> think of is, make the HWPOISON flag apply at page_size level, instead
>> of always set at the compound head. At least from hugetlb's
>> perspective, is it a good idea?
> Many years ago someone looked at breaking up hugetlb pages
> when a memory error occurred so that just 4K was lost instead
> of the entire huge page. At that time the conclusion was that
> doing so would require locks to be taken/released around all
> hugetlb map/unmap operations. An unacceptable performance
> issue for common operations to handle very rare memory error
> events.
>
> I don't know if that is still true. There's been a lot of restructure
> to memory management code since then.
The HGM for hugetlbfs
<https://lore.kernel.org/linux-mm/20230306191944.GA15773@monkey/#r>
project attempted this as well.
https://lore.kernel.org/linux-mm/20230306191944.GA15773@monkey/
-jan
>
> -Tony
>
>
next prev parent reply other threads:[~2024-10-16 0:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 4:39 [RFC PATCH v1 0/2] Userspace Can Control Memory Failure Recovery Jiaqi Yan
2024-09-24 4:39 ` [RFC PATCH v1 1/2] mm/memory-failure: introduce global MFR policy Jiaqi Yan
2024-10-02 23:50 ` jane.chu
2024-10-03 23:51 ` Jiaqi Yan
2024-10-07 17:24 ` jane.chu
2024-10-10 23:21 ` Jiaqi Yan
2024-10-11 18:28 ` jane.chu
2024-10-11 19:44 ` Luck, Tony
2024-10-11 20:15 ` jane.chu
2024-10-15 23:45 ` Jiaqi Yan
2024-10-15 23:56 ` Luck, Tony
2024-10-16 0:19 ` jane.chu [this message]
2024-10-11 7:04 ` Miaohe Lin
2024-10-15 23:58 ` Jiaqi Yan
2024-09-24 4:39 ` [RFC PATCH v1 2/2] docs: mm: add enable_hard_offline sysctl Jiaqi Yan
2024-10-02 15:02 ` [RFC PATCH v1 0/2] Userspace Can Control Memory Failure Recovery Jason Gunthorpe
2024-10-03 22:45 ` Jiaqi Yan
2024-10-03 22:58 ` Luck, Tony
2024-10-03 23:19 ` Jiaqi Yan
2024-10-03 23:19 ` Jason Gunthorpe
2024-10-04 18:32 ` 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=5720bfe9-fb81-49e4-adb4-7b017cf759bb@oracle.com \
--to=jane.chu@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=ankita@nvidia.com \
--cc=duenwen@google.com \
--cc=jgg@nvidia.com \
--cc=jiaqiyan@google.com \
--cc=jthoughton@google.com \
--cc=linmiaohe@huawei.com \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=peterx@redhat.com \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).