Re: [PATCH v5 16/26] nvme: refactor prp mapping

2020-03-25 Thread Maxim Levitsky
On Mon, 2020-03-16 at 00:51 -0700, Klaus Birkelund Jensen wrote: > On Feb 12 13:44, Maxim Levitsky wrote: > > On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote: > > > Refactor nvme_map_prp and allow PRPs to be located in the CMB. The logic > > > ensures that if some of the PRP is in the CMB, al

Re: [PATCH v5 16/26] nvme: refactor prp mapping

2020-03-16 Thread Klaus Birkelund Jensen
On Feb 12 13:44, Maxim Levitsky wrote: > On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote: > > Refactor nvme_map_prp and allow PRPs to be located in the CMB. The logic > > ensures that if some of the PRP is in the CMB, all of it must be located > > there, as per the specification. > > To be h

Re: [PATCH v5 16/26] nvme: refactor prp mapping

2020-02-12 Thread Maxim Levitsky
On Tue, 2020-02-04 at 10:51 +0100, Klaus Jensen wrote: > Refactor nvme_map_prp and allow PRPs to be located in the CMB. The logic > ensures that if some of the PRP is in the CMB, all of it must be located > there, as per the specification. To be honest this looks like not refactoring but a bugfix

[PATCH v5 16/26] nvme: refactor prp mapping

2020-02-04 Thread Klaus Jensen
Refactor nvme_map_prp and allow PRPs to be located in the CMB. The logic ensures that if some of the PRP is in the CMB, all of it must be located there, as per the specification. Also combine nvme_dma_{read,write}_prp into a single nvme_dma_prp that takes an additional DMADirection parameter. Sig