linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: David Rientjes <rientjes@google.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Rik van Riel <riel@redhat.com>, Nick Piggin <npiggin@suse.de>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	linux-mm@kvack.org
Subject: Re: [patch -mm v2 04/10] oom: remove special handling for pagefault ooms
Date: Tue, 2 Mar 2010 08:55:32 +0900	[thread overview]
Message-ID: <20100302085532.ff9d3cf4.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1003010159420.26824@chino.kir.corp.google.com>

On Mon, 1 Mar 2010 02:04:07 -0800 (PST)
David Rientjes <rientjes@google.com> wrote:

> On Mon, 1 Mar 2010, Balbir Singh wrote:
> 
> > > diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> > > --- a/mm/oom_kill.c
> > > +++ b/mm/oom_kill.c
> > > @@ -580,6 +580,44 @@ void clear_zonelist_oom(struct zonelist *zonelist, gfp_t gfp_mask)
> > >  }
> > > 
> > >  /*
> > > + * Try to acquire the oom killer lock for all system zones.  Returns zero if a
> > > + * parallel oom killing is taking place, otherwise locks all zones and returns
> > > + * non-zero.
> > > + */
> > > +static int try_set_system_oom(void)
> > > +{
> > > +	struct zone *zone;
> > > +	int ret = 1;
> > > +
> > > +	spin_lock(&zone_scan_lock);
> > > +	for_each_populated_zone(zone)
> > > +		if (zone_is_oom_locked(zone)) {
> > > +			ret = 0;
> > > +			goto out;
> > > +		}
> > > +	for_each_populated_zone(zone)
> > > +		zone_set_flag(zone, ZONE_OOM_LOCKED);
> > > +out:
> > > +	spin_unlock(&zone_scan_lock);
> > > +	return ret;
> > > +}
> > 
> > Isn't this an overkill, if pagefault_out_of_memory() does nothing and
> > oom takes longer than anticipated, we might end up looping, no?
> > Aren't we better off waiting for OOM to finish and retry the
> > pagefault?
> > 
> 
> I agree, I can add schedule_timeout_uninterruptible(1) so we decrease the 
> loop while waiting for the parallel oom kill to happen.  It's not overkill 
> because we want to avoid needlessly killing tasks when killing one will 
> already free memory which is hopefully usable by the pagefault.  This 
> merely covers the race between a parallel oom kill calling out_of_memory() 
> and setting TIF_MEMDIE for a task which would make the following 
> out_of_memory() call in pagefault_out_of_memory() a no-op anyway.
> 
> > And like Kame said the pagefault code in memcg is undergoing a churn,
> > we should revisit those parts later. I am yet to review that
> > patchset though.
> > 
> 
> Kame said earlier it would be no problem to rebase his memcg oom work on 
> mmotm if my patches were merged.
> 

But I also said this patch cause regression.
I said it's ok to rabese to you series of patch. But about this patch,
No.


Thanks,
-Kame


--
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:[~2010-03-01 23:59 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 23:52 [patch -mm v2 00/10] oom killer rewrite David Rientjes
2010-02-26 23:53 ` [patch -mm v2 01/10] oom: filter tasks not sharing the same cpuset David Rientjes
2010-03-02  4:54   ` Balbir Singh
2010-02-26 23:53 ` [patch -mm v2 02/10] oom: sacrifice child with highest badness score for parent David Rientjes
2010-03-02  4:54   ` Balbir Singh
2010-02-26 23:53 ` [patch -mm v2 03/10] oom: select task from tasklist for mempolicy ooms David Rientjes
2010-02-26 23:53 ` [patch -mm v2 04/10] oom: remove special handling for pagefault ooms David Rientjes
2010-03-01  1:12   ` KAMEZAWA Hiroyuki
2010-03-01 10:13     ` David Rientjes
2010-03-01 23:59       ` KAMEZAWA Hiroyuki
2010-03-02 23:55         ` David Rientjes
2010-03-03  0:24           ` KAMEZAWA Hiroyuki
2010-03-03  0:44             ` David Rientjes
2010-03-01  5:23   ` Balbir Singh
2010-03-01 10:04     ` David Rientjes
2010-03-01 23:55       ` KAMEZAWA Hiroyuki [this message]
2010-03-03  0:01         ` David Rientjes
2010-03-03  0:22           ` KAMEZAWA Hiroyuki
2010-03-03  0:38             ` David Rientjes
2010-03-03  0:44               ` KAMEZAWA Hiroyuki
2010-03-03  0:53                 ` David Rientjes
2010-03-03  0:58                   ` KAMEZAWA Hiroyuki
2010-03-03 23:27                     ` David Rientjes
2010-03-04  3:59                       ` KAMEZAWA Hiroyuki
2010-03-04  6:50                         ` David Rientjes
2010-03-04  7:00                           ` KAMEZAWA Hiroyuki
2010-03-04  9:50                             ` David Rientjes
2010-03-05  0:58                               ` KAMEZAWA Hiroyuki
2010-03-02  2:21   ` KAMEZAWA Hiroyuki
2010-03-02 23:59     ` David Rientjes
2010-02-26 23:53 ` [patch -mm v2 05/10] oom: badness heuristic rewrite David Rientjes
2010-02-26 23:53 ` [patch -mm v2 06/10] oom: deprecate oom_adj tunable David Rientjes
2010-02-26 23:53 ` [patch -mm v2 07/10] oom: replace sysctls with quick mode David Rientjes
2010-02-26 23:53 ` [patch -mm v2 08/10] oom: avoid oom killer for lowmem allocations David Rientjes
2010-02-26 23:53 ` [patch -mm v2 09/10] oom: remove unnecessary code and cleanup David Rientjes
2010-02-26 23:53 ` [patch -mm v2 10/10] oom: default to killing current for pagefault ooms 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=20100302085532.ff9d3cf4.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=riel@redhat.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