From: Christoph Hellwig <hch@infradead.org>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Joerg Roedel <jroedel@suse.de>, Andy Lutomirski <luto@kernel.org>,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 3/9] dma: Add dma_virt_ops
Date: Wed, 11 Jan 2017 00:56:25 -0800 [thread overview]
Message-ID: <20170111085625.GA15575@infradead.org> (raw)
In-Reply-To: <20170111005648.14988-4-bart.vanassche@sandisk.com>
> +lib-$(CONFIG_HAS_DMA) += dma-virt.o
There probably should be a config option for it for two reasons:
- do not bloat kernels that don't need it.
- the feature can only work for 32-bit architectures or for
64-bit architectures that set ARCH_DMA_ADDR_T_64BIT…
Altenatiely this option would have to force
ARCH_DMA_ADDR_T_64BIT when not yet set for 64-bit architectures.
And yes, this is currently broken already for, but we'd better fix it.
next prev parent reply other threads:[~2017-01-11 8:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 0:56 [PATCH 0/9] IB: Optimize DMA mapping Bart Van Assche
2017-01-11 0:56 ` [PATCH 3/9] dma: Add dma_virt_ops Bart Van Assche
2017-01-11 8:56 ` Christoph Hellwig [this message]
2017-01-12 0:07 ` Bart Van Assche
2017-01-11 0:56 ` [PATCH 4/9] IB/hf1: Remove DMA mapping code Bart Van Assche
2017-01-11 0:56 ` [PATCH 5/9] IB/qib: " Bart Van Assche
2017-01-12 13:15 ` Leon Romanovsky
2017-01-11 0:56 ` [PATCH 6/9] IB: Use dma_virt_ops instead of duplicating it Bart Van Assche
2017-01-12 13:17 ` Leon Romanovsky
2017-01-11 0:56 ` [PATCH 7/9] RDS: IB: Remove an unused structure member Bart Van Assche
2017-01-11 1:21 ` santosh.shilimkar
2017-01-11 0:56 ` [PATCH 8/9] IB: Convert ib_dma_*_coherent() argument type from u64 into dma_addr_t Bart Van Assche
2017-01-12 13:12 ` Leon Romanovsky
2017-01-11 0:56 ` [PATCH 9/9] treewide: Inline ib_dma_map_*() functions Bart Van Assche
2017-01-12 11:45 ` Sagi Grimberg
2017-01-12 13:09 ` Leon Romanovsky
2017-01-11 1:28 ` [PATCH 0/9] IB: Optimize DMA mapping santosh.shilimkar
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=20170111085625.GA15575@infradead.org \
--to=hch@infradead.org \
--cc=bart.vanassche@sandisk.com \
--cc=borntraeger@de.ibm.com \
--cc=dledford@redhat.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mst@redhat.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