From: Jason Gunthorpe <jgg@mellanox.com>
To: Jerome Glisse <jglisse@redhat.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
lsf-pc@lists.linux-foundation.org,
Christoph Hellwig <hch@infradead.org>,
Michal Hocko <mhocko@kernel.org>, Linux MM <linux-mm@kvack.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
linux-nvdimm@lists.01.org
Subject: Re: [LSF/MM TOPIC] Filesystem-DAX, page-pinning, and RDMA
Date: Thu, 1 Feb 2018 16:27:20 -0700 [thread overview]
Message-ID: <20180201232720.GX23352@mellanox.com> (raw)
In-Reply-To: <20180129233324.GC4526@redhat.com>
On Mon, Jan 29, 2018 at 06:33:25PM -0500, Jerome Glisse wrote:
> Between i would also like to participate, in my view the burden should
> be on GUP users, so if hardware is not ODP capable then you should at
> least be able to kill the mapping/GUP and force the hardware to redo a
> GUP if it get any more transaction on affect umem. Can non ODP hardware
> do that ? Or is it out of the question ?
For RDMA we can have the HW forcibly tear down the MR, but it is
incredibly disruptive and nobody running applications would be happy
with this outcome.
Jason
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2018-02-01 23:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 3:56 Dan Williams
2018-01-25 4:01 ` Bart Van Assche
2018-01-25 7:02 ` Dan Williams
2018-01-25 16:08 ` Jason Gunthorpe
2018-01-25 16:47 ` hch
2018-01-25 7:23 ` Christoph Hellwig
2018-01-25 16:08 ` Jason Gunthorpe
2018-01-25 16:47 ` Christoph Hellwig
2018-01-27 2:50 ` Dan Williams
2019-04-05 23:01 ` Jason Gunthorpe
2018-01-29 23:33 ` Jerome Glisse
2018-02-01 23:27 ` Jason Gunthorpe [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=20180201232720.GX23352@mellanox.com \
--to=jgg@mellanox.com \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=jglisse@redhat.com \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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