linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Paul Jackson <pj@sgi.com>
Cc: menage@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 21:24:11 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.0.9999.0709252119130.32009@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.0.9999.0709252104180.30932@chino.kir.corp.google.com>

On Tue, 25 Sep 2007, David Rientjes wrote:

> 	void dump_tasks(const struct mem_cgroup *mem)
> 	{
> 		struct task_struct *g, *p;
> 
> 		do_each_thread(g, p) {
> 			...
> 
> 			if (!task_in_mem_cgroup(p, mem)
> 				continue;
> 			if (!cpuset_mems_allowed_intersects(current, p))
> 				continue;
> 
> 			/* show the task information */
> 
> 		} while_each_thread(g, p);
> 	}
> 

By the way, the only reason I didn't code it like this was because tasks 
that overlap nodes in mems_allowed with the OOM-triggering task aren't 
necessarily excluded from being OOM killed, as I mentioned.  In other 
words, coding it like the above opens up the possibility of filtering the 
task that ends up getting killed.  Not a good idea.

Tasks that aren't in the same mem_cgroup, however, are filtered from the 
dump because they are explicitly excluded from being a target.  The check 
for that is actually misplaced and currently appears in badness() when it 
should appear in select_bad_process().

--
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>

  reply	other threads:[~2007-09-26  4:24 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 [this message]
2007-09-26  4:37             ` Paul Jackson
2007-09-26  1:22       ` Paul Menage
2007-09-26  3:57         ` Paul Jackson
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=alpine.DEB.0.9999.0709252119130.32009@chino.kir.corp.google.com \
    --to=rientjes@google.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=pj@sgi.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