From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Bart Van Assche <Bart.VanAssche@wdc.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"hch@infradead.org" <hch@infradead.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"mhocko@kernel.org" <mhocko@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [LSF/MM TOPIC] Filesystem-DAX, page-pinning, and RDMA
Date: Thu, 25 Jan 2018 09:08:48 -0700 [thread overview]
Message-ID: <20180125160848.GE10706@ziepe.ca> (raw)
In-Reply-To: <CAPcyv4iERedTChineSd-9fYR-xOc6E4L-okj7OnCMmoUkMf0tA@mail.gmail.com>
On Wed, Jan 24, 2018 at 11:02:16PM -0800, Dan Williams wrote:
> No, in 3 dimensions since there is a need to support non-ODP RDMA
> hardware, hypervisors want to coordinate DMA for guests, and non-RDMA
> hardware also pins memory indefinitely like V4L2. So it's bigger than
> RDMA, but that will likely be the first consumer of this 'longterm
> pin' mechanism.
BTW, did you look at VFIO? I think it should also have this problem
right?
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>
next prev parent reply other threads:[~2018-01-25 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 3:56 [LSF/MM TOPIC] Filesystem-DAX, page-pinning, and RDMA Dan Williams
2018-01-25 4:01 ` Bart Van Assche
2018-01-25 7:02 ` Dan Williams
2018-01-25 16:08 ` Jason Gunthorpe [this message]
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
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=20180125160848.GE10706@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Bart.VanAssche@wdc.com \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).