Messages in this thread | | | Date | Wed, 17 Jan 2007 01:57:34 -0800 | From | Andrew Morton <> | Subject | Re: [RFC 0/8] Cpuset aware writeback |
| |
> On Wed, 17 Jan 2007 00:01:58 -0800 Paul Jackson <pj@sgi.com> wrote: > Andrew wrote: > > - consider going off-cpuset for critical allocations. > > We do ... in mm/page_alloc.c: > > * This is the last chance, in general, before the goto nopage. > * Ignore cpuset if GFP_ATOMIC (!wait) rather than fail alloc. > * See also cpuset_zone_allowed() comment in kernel/cpuset.c. > */ > page = get_page_from_freelist(gfp_mask, order, zonelist, alloc_flags); > > We also allow GFP_KERNEL requests to escape the current cpuset, to the nearest > enclosing mem_exclusive cpuset, which is typically a big cpuset covering most > of the system.
hrm. So how come NFS is getting oom-killings?
The oom-killer normally spews lots of useful stuff, including backtrace. For some reason that's not coming out for Christoph. Log facility level, perhaps? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |