Where's the urge to remove merge_bvec coming from? I think it's premature to touch this, and that the other changes, if fixed and integrated, should be allowed to bed themselves down first. Ideally every bio would be the best size on submission and no bio would ever need to be split. But there is a cost involved in calculating the best size - we use merge_bvec for this, which gives a (probable) maximum size. It's usually very cheap to calculate - but not always. [In dm, we permit some situations where the answer we give will turn out to be wrong, but ensure dm will always fix up those particular cases itself later and still process the over-sized bio correctly.] Similarly there is a performance penalty incurred when the size is wrong - the bio has to be split, requiring memory, potential delays etc. There is a trade-off between those two, and our experience with the current code has that tilted strongly in favour of using merge_bvec all the time. The wasted overhead in cases where it is of no benefit seem to be outweighed by the benefit where it does avoid lots of splitting and help filesystems optimise their behaviour. If the splitting mechanism is changed as proposed, then that balance might shift. My gut feeling though is that any shift would strengthen the case for merge_bvec. Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
