From: Jane Chu <jane.chu@oracle.com>
To: David Rientjes <rientjes@google.com>,
"Luck, Tony" <tony.luck@intel.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Peter Xu <peterx@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>
Cc: Matthew Wilcox <willy@infradead.org>,
Borislav Petkov <bp@alien8.de>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
linux-edac@vger.kernel.org, linux-mm@kvack.org,
linux-nvdimm@lists.01.org,
"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [RFC] Make the memory failure blast radius more precise
Date: Wed, 24 Jun 2020 13:57:17 -0700 [thread overview]
Message-ID: <19ffec14-28c7-fddc-3042-6ccb8d4e83fa@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2006232114100.97817@chino.kir.corp.google.com>
Hi, David,
On 6/23/2020 9:32 PM, David Rientjes wrote:
> I don't want to hijack Matthew's thread which is primarily about DAX, but
> did get intrigued by your concerns about hugetlbfs page poisoning. We can
> fork the thread off here to discuss only the hugetlb application of this
> if it makes sense to you or you'd like to collaborate on it as well.
hugetlbfs is not supported in DAX, are you planning to add support?
thanks,
-jane
next prev parent reply other threads:[~2020-06-24 20:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 20:17 [RFC] Make the memory failure blast radius more precise Matthew Wilcox
2020-06-23 21:48 ` Dan Williams
2020-06-23 22:04 ` Luck, Tony
2020-06-23 22:17 ` Matthew Wilcox
2020-06-23 22:26 ` Luck, Tony
2020-06-23 22:40 ` Matthew Wilcox
2020-06-24 0:01 ` Darrick J. Wong
2020-06-24 12:10 ` Matthew Wilcox
2020-06-24 23:21 ` Dan Williams
2020-06-25 0:17 ` Matthew Wilcox
2020-06-25 1:18 ` Dan Williams
2020-06-24 21:22 ` Jane Chu
2020-06-25 0:13 ` Luck, Tony
2020-06-25 16:23 ` Jane Chu
2020-06-24 4:32 ` David Rientjes
2020-06-24 20:57 ` Jane Chu [this message]
2020-06-24 22:01 ` David Rientjes
2020-06-25 2:16 ` 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=19ffec14-28c7-fddc-3042-6ccb8d4e83fa@oracle.com \
--to=jane.chu@oracle.com \
--cc=aarcange@redhat.com \
--cc=bp@alien8.de \
--cc=darrick.wong@oracle.com \
--cc=dgilbert@redhat.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mike.kravetz@oracle.com \
--cc=naoya.horiguchi@nec.com \
--cc=peterx@redhat.com \
--cc=rientjes@google.com \
--cc=tony.luck@intel.com \
--cc=willy@infradead.org \
/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).