From: "hch@lst.de" <hch@lst.de>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: "hch@lst.de" <hch@lst.de>,
Thomas Hellstrom <thellstrom@vmware.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yong.zhi@intel.com" <yong.zhi@intel.com>,
"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"syeh@vmware.com" <syeh@vmware.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"bingbu.cao@intel.com" <bingbu.cao@intel.com>,
"imre.deak@intel.com" <imre.deak@intel.com>,
"tian.shu.qiu@intel.com" <tian.shu.qiu@intel.com>,
"jian.xu.zheng@intel.com" <jian.xu.zheng@intel.com>,
"shiraz.saleem@intel.com" <shiraz.saleem@intel.com>,
"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] lib/scatterlist: Provide a DMA page iterator
Date: Thu, 17 Jan 2019 10:30:01 +0100 [thread overview]
Message-ID: <20190117093001.GB31303@lst.de> (raw)
In-Reply-To: <20190116172436.GM22045@ziepe.ca>
On Wed, Jan 16, 2019 at 10:24:36AM -0700, Jason Gunthorpe wrote:
> The fact is there is 0 industry interest in using RDMA on platforms
> that can't do HW DMA cache coherency - the kernel syscalls required to
> do the cache flushing on the IO path would just destroy performance to
> the point of making RDMA pointless. Better to use netdev on those
> platforms.
In general there is no syscall required for doing cache flushing, you
just issue the proper instructions directly from userspace.
> The reality is that *all* the subsytems doing DMA kernel bypass are
> ignoring the DMA mapping rules, I think we should support this better,
> and just accept that user space DMA will not be using syncing. Block
> access in cases when this is required, otherwise let it work as is
> today.
In that case we just need to block userspace DMA access entirely.
Which given the amount of problems it creates sounds like a pretty
good idea anyway.
next prev parent reply other threads:[~2019-01-17 9:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 22:35 [PATCH] lib/scatterlist: Provide a DMA page iterator Jason Gunthorpe
2019-01-05 2:37 ` kbuild test robot
2019-01-05 3:21 ` Jason Gunthorpe
2019-01-10 23:42 ` Jason Gunthorpe
2019-01-14 9:48 ` Christoph Hellwig
2019-01-15 14:17 ` Thomas Hellstrom
2019-01-15 14:24 ` Christian König
2019-01-15 15:20 ` hch
2019-01-15 18:03 ` Thomas Hellstrom
2019-01-15 18:31 ` hch
2019-01-15 19:13 ` Koenig, Christian
2019-01-15 20:58 ` hch
2019-01-16 7:09 ` Thomas Hellstrom
2019-01-16 7:28 ` Koenig, Christian
2019-01-16 10:14 ` Daniel Vetter
2019-01-16 16:06 ` hch
2019-01-16 16:36 ` Daniel Stone
2019-01-15 21:25 ` Jason Gunthorpe
2019-01-16 10:40 ` Christian König
2019-01-16 16:11 ` hch
2019-01-16 17:24 ` Jason Gunthorpe
2019-01-17 9:30 ` hch [this message]
2019-01-17 10:47 ` Thomas Hellstrom
2019-01-17 15:54 ` Jason Gunthorpe
2019-01-12 18:27 ` Shiraz Saleem
2019-01-12 18:37 ` Jason Gunthorpe
2019-01-12 19:03 ` Shiraz Saleem
2019-01-14 9:46 ` Christoph Hellwig
2019-01-14 22:16 ` Jason Gunthorpe
2019-02-07 23:23 ` Sakari Ailus
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=20190117093001.GB31303@lst.de \
--to=hch@lst.de \
--cc=bingbu.cao@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=jgg@ziepe.ca \
--cc=jian.xu.zheng@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=shiraz.saleem@intel.com \
--cc=syeh@vmware.com \
--cc=thellstrom@vmware.com \
--cc=tian.shu.qiu@intel.com \
--cc=yong.zhi@intel.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 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).