For awhile now, many of the GEM code paths have allocated page or object arrays with the slab allocator. This is nice and fast, but won't work well if memory is fragmented, since the slab allocator works with physically contiguous memory (i.e. order > 2 allocations are likely to fail fairly early after booting and doing some work). This patch works around the issue by falling back to vmalloc for >PAGE_SIZE allocations. This is ugly, but much less work than chaining a bunch of pages together by hand (suprisingly there's not a bunch of generic kernel helpers for this yet afaik). vmalloc space is somewhat precious on 32 bit kernels, but our allocations shouldn't be big enough to cause problems, though they're routinely more than a page. Note that this patch doesn't address the unchecked alloc-based-on-ioctl-args in GEM; that needs to be fixed in a separate patch. Also, I've deliberately ignored the DRM's "area" junk. I don't think anyone actually uses it anymore and I'm hoping it gets ripped out soon. [Updated: removed size arg to new free function. We could unify the free functions as well once the DRM mem tracking is ripped out.] fd.o bug #20152 (part 1/3) Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Eric Anholt <eric@anholt.net> |
||
---|---|---|
.. | ||
Kbuild | ||
drm.h | ||
drmP.h | ||
drm_core.h | ||
drm_crtc.h | ||
drm_crtc_helper.h | ||
drm_edid.h | ||
drm_hashtab.h | ||
drm_memory.h | ||
drm_memory_debug.h | ||
drm_mode.h | ||
drm_os_linux.h | ||
drm_pciids.h | ||
drm_sarea.h | ||
drm_sman.h | ||
i810_drm.h | ||
i830_drm.h | ||
i915_drm.h | ||
mga_drm.h | ||
r128_drm.h | ||
radeon_drm.h | ||
savage_drm.h | ||
sis_drm.h | ||
via_drm.h |