On Tue, May 16, 2017 at 12:53:52PM +0200, Michal Hocko wrote: > On Tue 16-05-17 10:31:19, Chris Wilson wrote: > > On Tue, May 16, 2017 at 11:06:06AM +0200, Michal Hocko wrote: > > > From: Michal Hocko <mhocko@xxxxxxxx> > > > > > > drm_malloc* has grown their own kmalloc with vmalloc fallback > > > implementations. MM has grown kvmalloc* helpers in the meantime. Let's > > > use those because it a) reduces the code and b) MM has a better idea > > > how to implement fallbacks (e.g. do not vmalloc before kmalloc is tried > > > with __GFP_NORETRY). > > > > Better? The same idea. The only difference I was reluctant to hand out > > large pages for long lived objects. If that's the wisdom of the core mm, > > so be it. > > vmalloc tends to fragment physical memory more os it is preferable to > try the physically contiguous request first and only fall back to > vmalloc if the first attempt would be too costly or it fails. Not relevant for the changelog in this patch, but it would be nice to have that written in kvmalloc() as to why the scatterring of 4k vmapped pages prevents defragmentation when compared to allocating large pages. I have vague recollections of seeing the conversation, but a summary as to the reason why kvmalloc prefers large pages will be good for future reference. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
