Re: [PATCH RFC 0/2] mempool based chained scatterlist alloc/free api api

2016-03-16 Thread Christoph Hellwig
On Tue, Mar 15, 2016 at 04:12:03PM -0700, James Bottomley wrote: > motion. If you add in one patch and remove in another the code motion > trackers don't see it. Agreed, having the move in a single patch would be nice. > Thirdly, are you sure the pool structure for NVMe should be the same as > f

Re: [PATCH RFC 0/2] mempool based chained scatterlist alloc/free api api

2016-03-15 Thread Ming Lin
On Tue, 2016-03-15 at 16:12 -0700, James Bottomley wrote: > On Tue, 2016-03-15 at 15:39 -0700, Ming Lin wrote: > > From: Ming Lin > > > > Hi list, > > > > This moves the mempool based chained scatterlist alloc/free code > > from > > scsi_lib.c to lib/scatterlist.c. > > > > So other drivers(for

Re: [PATCH RFC 0/2] mempool based chained scatterlist alloc/free api api

2016-03-15 Thread James Bottomley
On Tue, 2016-03-15 at 15:39 -0700, Ming Lin wrote: > From: Ming Lin > > Hi list, > > This moves the mempool based chained scatterlist alloc/free code from > scsi_lib.c to lib/scatterlist.c. > > So other drivers(for example, the under development NVMe over fabric > drivers) can also use it. >

[PATCH RFC 0/2] mempool based chained scatterlist alloc/free api api

2016-03-15 Thread Ming Lin
From: Ming Lin Hi list, This moves the mempool based chained scatterlist alloc/free code from scsi_lib.c to lib/scatterlist.c. So other drivers(for example, the under development NVMe over fabric drivers) can also use it. Ming Lin (2): scatterlist: add mempool based chained SG alloc/free api