The size is configurable but typically 512KB (that's the default). Refer to bio payload sounds really dangerous but it may be possible in some tricky way. but at the moment I am not sure how the implementation would be.
Is there some fancy function that is like memcpy but actually "move" the ownership? - Akira On 2015/02/21 0:50, Joe Thornber wrote: > On Sat, Feb 21, 2015 at 12:25:53AM +0900, Akira Hayakawa wrote: >> Yes. > How big are your log chunks? Presumably they're relatively small (eg, > 256k). In which case you can optimise for the common case where you > have enough bios to hand to build your log chunk by just referencing > the bio payloads, rather than copying. It's only the last bit of io > in a burst that should be using this copying slow path. > > - Joe -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
