From: Christopher Lameter <cl@linux.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-rdma <linux-rdma@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>, Michal Hocko <mhocko@kernel.org>
Subject: Re: [LSFMM] RDMA data corruption potential during FS writeback
Date: Mon, 21 May 2018 13:59:01 +0000 [thread overview]
Message-ID: <0100016382ff04b5-3b884d8b-33c5-471e-b7fa-b1c19a3106fe-000000@email.amazonses.com> (raw)
In-Reply-To: <c8861cbb-5b2e-d6e2-9c89-66c5c92181e6@nvidia.com>
On Fri, 18 May 2018, John Hubbard wrote:
> > In other words, get_user_pages_longterm() is just a short term
> > band-aid for RDMA until we can get that infrastructure built. We don't
> > need to go down any mmu-notifier rabbit holes.
> >
>
> git grep claims that break_layouts is so far an XFS-only feature, though.
> Were there plans to fix this for all filesystems?
break_layouts? This sounds from my perspective like a mmu notifier
callback with slightly different semantics. Maybe add another callback to
generalize that functionality?
prev parent reply other threads:[~2018-05-21 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 14:37 [LSFMM] RDMA data corruption potential during FS writeback Christopher Lameter
2018-05-18 15:49 ` Jason Gunthorpe
2018-05-18 16:47 ` Christopher Lameter
2018-05-18 17:36 ` Jason Gunthorpe
2018-05-18 20:23 ` Dan Williams
2018-05-19 2:33 ` John Hubbard
2018-05-19 3:24 ` Jason Gunthorpe
2018-05-19 3:51 ` Dan Williams
2018-05-19 5:38 ` John Hubbard
2018-05-21 14:38 ` Matthew Wilcox
2018-05-23 23:03 ` John Hubbard
2018-05-21 13:37 ` Christopher Lameter
2018-05-21 13:59 ` Christopher Lameter [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=0100016382ff04b5-3b884d8b-33c5-471e-b7fa-b1c19a3106fe-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=dan.j.williams@intel.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mhocko@kernel.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).