Nate Diller wrote on Thursday, December 07, 2006 1:46 PM > the current code is straightforward and obviously correct. you want > to make the alloc/dealloc paths more complex, by special-casing for an > arbitrary limit of "small" I/O, AFAICT. of *course* you can expect > less overhead when you're doing one large I/O vs. two small ones, > that's the whole reason we have all this code to try to coalesce > contiguous I/O, do readahead, swap page clustering, etc. we *want* > more complexity if it will get us bigger I/Os. I don't see why we > want more complexity to reduce the *inherent* penalty of doing smaller > ones.
You should check out the latest proposal from Jens Axboe which treats all biovec size the same and stuff it along with struct bio. I think it is a better approach than my first cut of special casing 1 segment biovec. His patch will speed up all sized I/O. - Ken - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/