From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paul Jackson <pj@sgi.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Simon Derr <Simon.Derr@bull.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.12-rc1] cpusets special case GFP_ATOMIC allocs
Date: Sun, 27 Mar 2005 16:59:37 +1000 [thread overview]
Message-ID: <424659D9.9000705@yahoo.com.au> (raw)
In-Reply-To: <20050327065222.25762.37675.sendpatchset@sam.engr.sgi.com>
Paul Jackson wrote:
> Stringent enforcement of cpuset memory placement could cause
> the kernel to panic on a GFP_ATOMIC (!wait) memory allocation,
> even though memory was available elsewhere in the system.
>
> Relax the cpuset constraint, on the last zone loop in
> mm/page_alloc.c:__alloc_pages(), for ATOMIC requests.
>
Kernel should not panic if a GFP_ATOMIC allocation fails.
Where is this happening?
next prev parent reply other threads:[~2005-03-27 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 6:52 [PATCH 2.6.12-rc1] cpusets special case GFP_ATOMIC allocs Paul Jackson
2005-03-27 6:59 ` Nick Piggin [this message]
2005-03-27 9:14 ` Paul Jackson
2005-03-28 7:03 ` [PATCH 2.6.12-rc1] cpusets GFP_ATOMIC fix: tonedown panic comment Paul Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=424659D9.9000705@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.