On Fri, Nov 06, 2020 at 07:19:31PM +0100, Christoph Hellwig wrote:
> Hi Jason,
>
> this series switches the RDMA core to opencode the special case of
> devices bypassing the DMA mapping in the RDMA ULPs. The virt ops
> have caused a bit of trouble due to the P2P code node working with
> them due
On 11/17/20 2:50 AM, Ka-Cheong Poon wrote:
On 11/13/20 1:36 AM, santosh.shilim...@oracle.com wrote:
+ Ka-Cheong
On 11/12/20 5:23 AM, Jason Gunthorpe wrote:
On Thu, Nov 12, 2020 at 10:40:30AM +0100, Christoph Hellwig wrote:
ping?
On Fri, Nov 06, 2020 at 07:19:31PM +0100, Christoph Hellwig wro
On 11/13/20 1:36 AM, santosh.shilim...@oracle.com wrote:
+ Ka-Cheong
On 11/12/20 5:23 AM, Jason Gunthorpe wrote:
On Thu, Nov 12, 2020 at 10:40:30AM +0100, Christoph Hellwig wrote:
ping?
On Fri, Nov 06, 2020 at 07:19:31PM +0100, Christoph Hellwig wrote:
Hi Jason,
this series switches the RDM
Fixes: 551199aca1c3 ("lib/dma-virt: Add dma_virt_ops")
Note that the drivers had open coded versions of this earlier. I think
this goes back to the addition of the qib driver which is now gone
or the addition of the hfi1 or rxe drivers for something that still
matters
Christoph,Jason
I built
On Thu, Nov 12, 2020 at 01:39:06PM -0400, Jason Gunthorpe wrote:
> On Thu, Nov 12, 2020 at 06:09:56PM +0100, Christoph Hellwig wrote:
> > On Thu, Nov 12, 2020 at 12:59:35PM -0400, Jason Gunthorpe wrote:
> > > RMDA/sw: Don't allow drivers using dma_virt_ops on highmem configs
> >
> > I think this
On Thu, Nov 12, 2020 at 06:09:56PM +0100, Christoph Hellwig wrote:
> On Thu, Nov 12, 2020 at 12:59:35PM -0400, Jason Gunthorpe wrote:
> > RMDA/sw: Don't allow drivers using dma_virt_ops on highmem configs
>
> I think this one actually is something needed in 5.10 and -stable.
Done, I added a
Fix
+ Ka-Cheong
On 11/12/20 5:23 AM, Jason Gunthorpe wrote:
On Thu, Nov 12, 2020 at 10:40:30AM +0100, Christoph Hellwig wrote:
ping?
On Fri, Nov 06, 2020 at 07:19:31PM +0100, Christoph Hellwig wrote:
Hi Jason,
this series switches the RDMA core to opencode the special case of
devices bypassing t
On Thu, Nov 12, 2020 at 12:59:35PM -0400, Jason Gunthorpe wrote:
> RMDA/sw: Don't allow drivers using dma_virt_ops on highmem configs
I think this one actually is something needed in 5.10 and -stable.
___
iommu mailing list
iommu@lists.linux-foundation.
On Fri, Nov 06, 2020 at 07:19:31PM +0100, Christoph Hellwig wrote:
> Hi Jason,
>
> this series switches the RDMA core to opencode the special case of
> devices bypassing the DMA mapping in the RDMA ULPs. The virt ops
> have caused a bit of trouble due to the P2P code node working with
> them due
On Thu, Nov 12, 2020 at 10:40:30AM +0100, Christoph Hellwig wrote:
> ping?
>
> On Fri, Nov 06, 2020 at 07:19:31PM +0100, Christoph Hellwig wrote:
> > Hi Jason,
> >
> > this series switches the RDMA core to opencode the special case of
> > devices bypassing the DMA mapping in the RDMA ULPs. The v
ping?
On Fri, Nov 06, 2020 at 07:19:31PM +0100, Christoph Hellwig wrote:
> Hi Jason,
>
> this series switches the RDMA core to opencode the special case of
> devices bypassing the DMA mapping in the RDMA ULPs. The virt ops
> have caused a bit of trouble due to the P2P code node working with
> th
Hi Jason,
this series switches the RDMA core to opencode the special case of
devices bypassing the DMA mapping in the RDMA ULPs. The virt ops
have caused a bit of trouble due to the P2P code node working with
them due to the fact that we'd do two dma mapping iterations for a
single I/O, but also
Hi Jason,
this series switches the RDMA core to opencode the special case of
devices bypassing the DMA mapping in the RDMA ULPs. The virt ops
have caused a bit of trouble due to the P2P code node working with
them due to the fact that we'd do two dma mapping iterations for a
single I/O, but also
13 matches
Mail list logo
