Re: [PATCH v2 13/20] nvme: refactor prp mapping

2019-11-25 Thread Beata Michalska
On Wed, 20 Nov 2019 at 09:39, Klaus Birkelund wrote: > > On Tue, Nov 12, 2019 at 03:23:43PM +, Beata Michalska wrote: > > Hi Klaus, > > > > On Tue, 15 Oct 2019 at 11:57, Klaus Jensen wrote: > > > > > > Instead of handling both QSGs and IOVs in multiple places, simply use > > > QSGs

Re: [PATCH v2 13/20] nvme: refactor prp mapping

2019-11-20 Thread Klaus Birkelund
On Tue, Nov 12, 2019 at 03:23:43PM +, Beata Michalska wrote: > Hi Klaus, > > On Tue, 15 Oct 2019 at 11:57, Klaus Jensen wrote: > > > > Instead of handling both QSGs and IOVs in multiple places, simply use > > QSGs everywhere by assuming that the request does not involve the > > controller

Re: [PATCH v2 13/20] nvme: refactor prp mapping

2019-11-12 Thread Beata Michalska
Hi Klaus, On Tue, 15 Oct 2019 at 11:57, Klaus Jensen wrote: > > Instead of handling both QSGs and IOVs in multiple places, simply use > QSGs everywhere by assuming that the request does not involve the > controller memory buffer (CMB). If the request is found to involve the > CMB, convert the

[PATCH v2 13/20] nvme: refactor prp mapping

2019-10-15 Thread Klaus Jensen
Instead of handling both QSGs and IOVs in multiple places, simply use QSGs everywhere by assuming that the request does not involve the controller memory buffer (CMB). If the request is found to involve the CMB, convert the QSG to an IOV and issue the I/O. The QSG is converted to an IOV by the dma