On Thu, Jan 23, 2014 at 02:47:10PM -0600, Christoph Lameter wrote: > On Wed, 22 Jan 2014, Mel Gorman wrote: > > > Large block support was proposed years ago by Christoph Lameter > > (http://lwn.net/Articles/232757/). I think I was just getting started > > in the community at the time so I do not recall any of the details. I do > > believe it motivated an alternative by Nick Piggin called fsblock though > > (http://lwn.net/Articles/321390/). At the very least it would be nice to > > know why neither were never merged for those of us that were not around > > at the time and who may not have the chance to dive through mailing list > > archives between now and March. > > It was rejected first because of the necessity of higher order page > allocations. Nick and I then added ways to virtually map higher order > pages if the page allocator could no longe provide those. > That'd be okish for 64-bit at least although it would show up as degraded performance in some cases when virtually contiguous buffers were used. Aside from the higher setup, access costs and teardown costs of a virtual contiguous buffer, the underlying storage would no longer gets a single buffer as part of the IO request. Would that not offset many of the advantages? -- Mel Gorman SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
