Re: properly communicate queue limits to the DMA layer v2

2019-07-16 Thread Martin K. Petersen
Christoph, > I think all the patches on the block side went into 5.2, but it's been > a while, so I might misremember.. I checked my notes and the reason I held them back was that I was waiting for a response from Broadcom wrt. the megaraid segment size limitation. However, given that mpt3sas

Re: properly communicate queue limits to the DMA layer v2

2019-07-15 Thread Christoph Hellwig
On Mon, Jul 15, 2019 at 01:33:11PM -0400, Martin K. Petersen wrote: > > Christoph, > > > Ping? What happened to this set of bug fixes? > > I thought they depended on Jens' tree? I think all the patches on the block side went into 5.2, but it's been a while, so I might misremember..

Re: properly communicate queue limits to the DMA layer v2

2019-07-15 Thread Martin K. Petersen
Christoph, > Ping? What happened to this set of bug fixes? I thought they depended on Jens' tree? -- Martin K. Petersen Oracle Linux Engineering

Re: properly communicate queue limits to the DMA layer v2

2019-07-15 Thread Christoph Hellwig
On Mon, Jun 17, 2019 at 02:19:52PM +0200, Christoph Hellwig wrote: > Hi Martin, > > we've always had a bit of a problem communicating the block layer > queue limits to the DMA layer, which needs to respect them when > an IOMMU that could merge segments is used. Unfortunately most > drivers don't

properly communicate queue limits to the DMA layer v2

2019-06-17 Thread Christoph Hellwig
Hi Martin, we've always had a bit of a problem communicating the block layer queue limits to the DMA layer, which needs to respect them when an IOMMU that could merge segments is used. Unfortunately most drivers don't get this right. Oddly enough we've been mostly getting away with it, although