From: Andrew Morton <akpm@linux-foundation.org>
To: Paul Jackson <pj@sgi.com>
Cc: David Rientjes <rientjes@google.com>,
peterz@infradead.org, ak@suse.de, clameter@cthulhu.engr.sgi.com,
linux-kernel@vger.kernel.org
Subject: Re: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
Date: Wed, 6 Jun 2007 01:00:02 -0700 [thread overview]
Message-ID: <20070606010002.2ff6fc98.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070606005610.a8c783ce.pj@sgi.com>
On Wed, 6 Jun 2007 00:56:10 -0700 Paul Jackson <pj@sgi.com> wrote:
> David wrote:
> > That is, unless you can guarantee this type of problem will not happen again
>
> Well, I certainly cannot guarantee that.
The only place I can think of where the kernel will sit there allocating
huge amounts of memory like this is in readahead.
next prev parent reply other threads:[~2007-06-06 8:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 22:39 [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally David Rientjes
2007-06-05 22:40 ` Christoph Lameter
2007-06-05 22:42 ` David Rientjes
2007-06-05 23:01 ` Paul Jackson
2007-06-05 23:16 ` David Rientjes
2007-06-05 23:19 ` Paul Jackson
2007-06-05 23:20 ` Christoph Lameter
2007-06-05 23:25 ` David Rientjes
2007-06-05 23:32 ` Christoph Lameter
2007-06-05 23:44 ` David Rientjes
2007-06-05 23:55 ` Paul Jackson
2007-06-06 1:17 ` David Rientjes
2007-06-06 1:20 ` Paul Jackson
2007-06-05 23:57 ` Christoph Lameter
2007-06-06 1:23 ` David Rientjes
2007-06-06 1:32 ` Christoph Lameter
2007-06-06 1:40 ` David Rientjes
2007-06-06 1:54 ` Christoph Lameter
2007-06-06 3:29 ` David Rientjes
2007-06-06 6:20 ` Peter Zijlstra
2007-06-06 6:42 ` David Rientjes
2007-06-06 7:09 ` Peter Zijlstra
2007-06-06 7:18 ` David Rientjes
2007-06-06 7:34 ` Paul Jackson
2007-06-06 7:39 ` Andrew Morton
2007-06-06 7:48 ` David Rientjes
2007-06-06 7:56 ` Paul Jackson
2007-06-06 8:00 ` Andrew Morton [this message]
2007-06-06 8:03 ` Peter Zijlstra
2007-06-06 7:56 ` Peter Zijlstra
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=20070606010002.2ff6fc98.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@suse.de \
--cc=clameter@cthulhu.engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pj@sgi.com \
--cc=rientjes@google.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox