On Thu, 23 Mar 2017, Chris Wilson <[email protected]> wrote: > On Thu, Mar 23, 2017 at 09:29:47AM +0200, Joonas Lahtinen wrote: >> On ke, 2017-03-22 at 22:34 +0000, Chris Wilson wrote: >> > Words cannot describe the embarrassment at creating a new gfp_t relaim to >> > only prevent the oomkiller but allow direct|kswapd reclaim, and then not >> > use it in the shmem_read_mapping_page_gfp(). >> > >> > Fixes: 24f8e00a8a2e ("drm/i915: Prefer to report ENOMEM rather than incur >> > the oom for gfx allocations") >> > Signed-off-by: Chris Wilson <[email protected]> >> > Cc: Joonas Lahtinen <[email protected]> >> > Cc: Daniel Vetter <[email protected]> >> >> Reviewed-by: Joonas Lahtinen <[email protected]> > > Thanks for not being smug, pushed.
He can't afford to be, he reviewed the commit being fixed! ;) BR, Jani. -- Jani Nikula, Intel Open Source Technology Center _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
