On Tue, Feb 11, 2014 at 06:15:57PM -0200, Marcelo Tosatti wrote: > On Tue, Feb 11, 2014 at 05:10:35PM +0000, Mel Gorman wrote: > > On Tue, Feb 11, 2014 at 01:26:29PM -0200, Marcelo Tosatti wrote: > > > > Or take a stab at allocating 1G pages at runtime. It would require > > > > finding properly aligned 1Gs worth of contiguous MAX_ORDER_NR_PAGES at > > > > runtime. I would expect it would only work very early in the lifetime of > > > > the system but if the user is willing to use kernel parameters to > > > > allocate them then it should not be an issue. > > > > > > Can be an improvement on top of the current patchset? Certain use-cases > > > require allocation guarantees (even if that requires kernel parameters). > > > > > > > Sure, they're not mutually exclusive. It would just avoid the need to > > create a new kernel parameter and use the existing interfaces. > > Yes, the problem is there is no guarantee is there? >
There is no guarantee anyway and early in the lifetime of the system there is going to be very little difference in success rates. In case there is a misunderstanding here, I'm not looking to NAK a series that adds another kernel parameter. If it was me, I would have tried runtime allocation first to avoid adding a new interface but it's a personal preference. -- Mel Gorman SUSE Labs -- 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/
