From: Jason Gunthorpe <jgg@nvidia.com>
To: Jiaqi Yan <jiaqiyan@google.com>
Cc: nao.horiguchi@gmail.com, linmiaohe@huawei.com,
tony.luck@intel.com, wangkefeng.wang@huawei.com,
jane.chu@oracle.com, akpm@linux-foundation.org,
osalvador@suse.de, rientjes@google.com, duenwen@google.com,
jthoughton@google.com, ankita@nvidia.com, peterx@redhat.com,
linux-mm@kvack.org
Subject: Re: [RFC PATCH v1 0/2] Userspace Can Control Memory Failure Recovery
Date: Wed, 2 Oct 2024 12:02:17 -0300 [thread overview]
Message-ID: <20241002150217.GR1365916@nvidia.com> (raw)
In-Reply-To: <20240924043924.3562257-1-jiaqiyan@google.com>
On Tue, Sep 24, 2024 at 04:39:18AM +0000, Jiaqi Yan wrote:
> So far I personally prefer the global MFR policy but open to feedbacks to both
> options, or new ideas.
Why? It seems more natural that only processe that can handle the
SIGBUS semantics would opt into them?
Jason
next prev parent reply other threads:[~2024-10-02 15:02 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
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 ` Jason Gunthorpe [this message]
2024-10-03 22:45 ` [RFC PATCH v1 0/2] Userspace Can Control Memory Failure Recovery 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=20241002150217.GR1365916@nvidia.com \
--to=jgg@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=ankita@nvidia.com \
--cc=duenwen@google.com \
--cc=jane.chu@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.