linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Andrea Arcangeli <andrea@suse.de>, Rik van Riel <riel@redhat.com>,
	linux-mm@kvack.org, Paul Jackson <pj@sgi.com>
Subject: Re: [patch 7/8] oom: only kill tasks that share zones with zonelist
Date: Wed, 19 Sep 2007 22:50:11 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.0.9999.0709192245070.22371@chino.kir.corp.google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709191156480.2241@schroedinger.engr.sgi.com>

On Wed, 19 Sep 2007, Christoph Lameter wrote:

> > +		for (vma = mm->mmap; vma; vma = vma->vm_next) {
> > +			unsigned long pfn;
> > +			struct zone *zone;
> > +
> > +			pfn = PFN_DOWN(vma->vm_start);
> > +			zone = page_zone(pfn_to_page(pfn));
> 
> This seems to assume that all pages in a vma are in the same zone? That is 
> not the case. On a NUMA system pages may be allocated round robin. Meaning 
> lots of zones are used that this approach does not catch.
> 

Setting the CONSTRAINT_MEMORY_POLICY case aside for a moment, what stops 
us from getting rid of taking callback_mutex and simply relying on the 
following to filter for candidate tasks:

	do_each_thread(g, p) {
		...
		/*
		 * Check if it will do any good to kill this task based
		 * on where it is allowed to allocate.
		 */
		if (!nodes_intersects(current->mems_allowed,
				      p->mems_allowed))
			continue;
		...
	} while_each_thread(g, p);

We shouldn't really be concerned with the changing cpuset states during 
out_of_memory() since we're only using it as a hint and we're not 
dereferencing current->cpuset or p->cpuset.  This eliminates the need for 
cpuset_{lock,unlock}() and cpuset_excl_nodes_overlap().

		David

--
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-20  5:50 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 18:24 [patch 0/8] oom killer updates David Rientjes
2007-09-19 18:24 ` [patch 1/8] oom: move prototypes to appropriate header file David Rientjes
2007-09-19 18:24   ` [patch 2/8] oom: move constraints to enum David Rientjes
2007-09-19 18:24     ` [patch 3/8] oom: save zonelist pointer for oom killer calls David Rientjes
2007-09-19 18:24       ` [patch 4/8] oom: serialize out of memory calls David Rientjes
2007-09-19 18:24         ` [patch 5/8] oom: add per-cpuset file oom_kill_asking_task David Rientjes
2007-09-19 18:24           ` [patch 6/8] oom: suppress extraneous stack and memory dump David Rientjes
2007-09-19 18:24             ` [patch 7/8] oom: only kill tasks that share zones with zonelist David Rientjes
2007-09-19 18:24               ` [patch 8/8] oom: do not check cpuset in badness scoring David Rientjes
2007-09-19 19:06                 ` Christoph Lameter
2007-09-19 18:57               ` [patch 7/8] oom: only kill tasks that share zones with zonelist Christoph Lameter
2007-09-20  5:50                 ` David Rientjes [this message]
2007-09-20 17:58                   ` Christoph Lameter
2007-09-20 18:37                     ` David Rientjes
2007-09-20 18:44                       ` Christoph Lameter
2007-09-19 19:00         ` [patch 4/8] oom: serialize out of memory calls Christoph Lameter
2007-09-19 20:30           ` David Rientjes
2007-09-19 19:05       ` [patch 3/8] oom: save zonelist pointer for oom killer calls Christoph Lameter
2007-09-19 20:37         ` David Rientjes
2007-09-19 20:54           ` Christoph Lameter
2007-09-19 21:20             ` David Rientjes
2007-09-19 23:51               ` Tim Pepper
2007-09-20  5:43                 ` David Rientjes
2007-09-20 17:56                   ` Christoph Lameter
2007-09-19 19:01   ` [patch 1/8] oom: move prototypes to appropriate header file Christoph Lameter
2007-09-19 19:49 ` [patch 0/8] oom killer updates Paul Jackson
2007-09-19 20:24   ` 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.0709192245070.22371@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrea@suse.de \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.org \
    --cc=pj@sgi.com \
    --cc=riel@redhat.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