From: Paul Jackson <pj@sgi.com>
To: Paul Menage <menage@google.com>
Cc: rientjes@google.com, akpm@linux-foundation.org, clameter@sgi.com,
balbir@linux.vnet.ibm.com, linux-mm@kvack.org
Subject: Re: [patch -mm 7/5] oom: filter tasklist dump by mem_cgroup
Date: Tue, 25 Sep 2007 20:57:46 -0700 [thread overview]
Message-ID: <20070925205746.dd74a887.pj@sgi.com> (raw)
In-Reply-To: <6599ad830709251822q371c4a62rfdf8911720edb86c@mail.gmail.com>
Paul M wrote:
> You could print any tasks that share memory nodes (in their cpuset)
> with the OOMing task.
Huh? I'm mystified. Why would printing tasks help avoid choosing
the wrong task to oom kill?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-09-26 3:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 17:13 [patch -mm 6/5] memcontrol: move mm_cgroup to header file David Rientjes
2007-09-25 17:13 ` [patch -mm 7/5] oom: filter tasklist dump by mem_cgroup David Rientjes
2007-09-25 17:48 ` Balbir Singh
2007-09-25 19:18 ` David Rientjes
2007-09-25 18:00 ` Paul Menage
2007-09-25 21:17 ` Christoph Lameter
2007-09-25 22:54 ` Paul Menage
2007-09-26 1:14 ` Paul Jackson
2007-09-26 1:20 ` David Rientjes
2007-09-26 3:56 ` Paul Jackson
2007-09-26 4:14 ` David Rientjes
2007-09-26 4:24 ` David Rientjes
2007-09-26 4:37 ` Paul Jackson
2007-09-26 1:22 ` Paul Menage
2007-09-26 3:57 ` Paul Jackson [this message]
2007-09-26 4:03 ` Paul Menage
2007-09-26 4:30 ` Paul Jackson
2007-09-25 17:18 ` [patch -mm 6/5] memcontrol: move mm_cgroup to header file Balbir Singh
2007-09-25 18:49 ` David Rientjes
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=20070925205746.dd74a887.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=menage@google.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