linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	linux-mm@kvack.org
Subject: Re: [patch -mm 2/2] oom: use old_mm for oom_disable_count in exec
Date: Tue, 7 Sep 2010 20:28:40 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1009072025360.4790@chino.kir.corp.google.com> (raw)
In-Reply-To: <20100907102532.C8EC.A69D9226@jp.fujitsu.com>

On Wed, 8 Sep 2010, KOSAKI Motohiro wrote:

> Don't mind. but general warning: If you continue to crappy objection, We
> are going to revert full of your userland breakage entirely instead minimum fix. 
> 

I'm not in the business of responding to your threats.  Unfortunately for 
your argument, you cannot cite a single example of a current user of 
/proc/pid/oom_adj that considers either (i) expected memory usage of the 
task, or (ii) system RAM capcacity, which would be required for that value 
to make any sense given the current implementation.

--
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-09-08  3:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02  0:00 [patch -mm 1/2] oom: protect oom_disable_count with task_lock in fork David Rientjes
2010-09-02  0:00 ` [patch -mm 2/2] oom: use old_mm for oom_disable_count in exec David Rientjes
2010-09-02  0:25   ` KOSAKI Motohiro
2010-09-02  0:50     ` David Rientjes
2010-09-08  2:44       ` KOSAKI Motohiro
2010-09-08  3:28         ` David Rientjes [this message]

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.2.00.1009072025360.4790@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    /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