From: David Woodhouse <dwmw2@infradead.org>
To: Christoph Hellwig <hch@lst.de>,
Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Doug Ledford <dledford@redhat.com>,
Sagi Grimberg <sagi@grimberg.me>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
virtualization@lists.linux-foundation.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] Move dma_ops from archdata into struct device
Date: Fri, 09 Dec 2016 19:13:34 +0000 [thread overview]
Message-ID: <1481310814.98151.11.camel@infradead.org> (raw)
In-Reply-To: <20161209182230.GC16622@lst.de>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On Fri, 2016-12-09 at 19:22 +0100, Christoph Hellwig wrote:
> We'll need a bit of a wieder audience for this I think..
>
> On Wed, Dec 07, 2016 at 05:11:28PM -0800, Bart Van Assche wrote:
> > Additionally, introduce set_dma_ops(). A later patch will introduce a
> > call to that function in the RDMA drivers that will be modified to use
> > dma_noop_ops.
>
> This looks good to me, and we had a lot of talk about this for other
> purposes for a while.
Hm, I'm not convinced we want per-device dma_ops. What we want is per-
device IOMMU ops, and any dma_ops are just a generic or platform-
specific (in some cases) wrapper around those. We shouldn't normally
need per-device DMA ops at all.
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5760 bytes --]
next prev parent reply other threads:[~2016-12-09 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <07c07529-4636-fafb-2598-7358d8a1460d@sandisk.com>
[not found] ` <58a325aa-8df7-6a2e-fadb-5d9031d8a1a0@sandisk.com>
2016-12-09 18:22 ` [PATCH 3/5] Move dma_ops from archdata into struct device Christoph Hellwig
2016-12-09 18:22 ` Christoph Hellwig
2016-12-09 19:13 ` David Woodhouse [this message]
2016-12-09 19:13 ` David Woodhouse
2016-12-09 19:46 ` Bart Van Assche
2016-12-09 19:46 ` Bart Van Assche
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=1481310814.98151.11.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=bart.vanassche@sandisk.com \
--cc=dledford@redhat.com \
--cc=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=virtualization@lists.linux-foundation.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