Hello, On Mon, Sep 10, 2012 at 05:22:12PM -0700, Kent Overstreet wrote: > This adds a pointer to the bvec array to struct bio_integrity_payload, > instead of the bvecs always being inline; then the bvecs are allocated > with bvec_alloc_bs(). > > This is needed eventually for immutable bio vecs - immutable bvecs > aren't useful if we still have to copy them, hence the need for the > pointer. Less code is always nice too, though. > > Also fix an amusing bug in bio_integrity_split() - struct bio_pair > doesn't have the integrity bvecs after the bio_integrity_payloads, so > there was a buffer overrun. The code was confusing pointers with arrays. Aside from what Martin and Vivek already pointed out, it generally looks okay to me but here are some thoughts. I'm quite doubtful how much we're gaining by this complex set of slabs and mempools approach compared to just using kmalloc + one mempool for the largest size. I can't think of anything to be gained in terms of cacheline hotness. In terms of memory usage too, we're proabably introducing more fragmentation with all the different slabs. Jens, what are you thoughts? For forward progress guarantee, single mempool per bioset serving the largest one is enough and we can significantly simplify the whole bioset thing. Thanks. -- tejun -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel