All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: Minchan Kim <minchan.kim@gmail.com>
Cc: David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Hugh Dickins <hughd@google.com>, Izik Eidus <ieidus@redhat.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	linux-mm@kvack.org
Subject: Re: [patch v2] oom: replace PF_OOM_ORIGIN with toggling oom_score_adj
Date: Thu, 14 Apr 2011 08:55:35 +0100	[thread overview]
Message-ID: <20110414085535.42559f6b@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <BANLkTi=EVZJVdYSx7LitP__gPH4PBEJy6w@mail.gmail.com>

On Thu, 14 Apr 2011 10:21:56 +0900
Minchan Kim <minchan.kim@gmail.com> wrote:
 
> Yes. We already have facilities for it(ex, task_lock, lock_task_sighand).
> And I think CAP_SYS_RESOURCE check in general function don't have a problem.
> 
> Of course, it adds unnecessary overhead slightly but it's not a hot
> path.  What's problem for you to go ahead?

Also, lock_task_sighand() would disable interrupts when acquiring
sighand->siglock, which this patch doesn't do, but should.

-- 
Matt Fleming, Intel Open Source Technology Center

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-04-14  7:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 18:33 [patch] oom: replace PF_OOM_ORIGIN with toggling oom_score_adj David Rientjes
2011-04-14  0:03 ` KOSAKI Motohiro
2011-04-14  0:41   ` [patch v2] " David Rientjes
2011-04-14  0:46     ` KOSAKI Motohiro
2011-04-14  1:09     ` Minchan Kim
2011-04-14  1:12       ` David Rientjes
2011-04-14  1:21         ` Minchan Kim
2011-04-14  7:55           ` Matt Fleming [this message]
2011-04-14 20:18     ` [patch v3] " David Rientjes
2011-04-15 22:35       ` Hugh Dickins
2011-04-15 23:03         ` David Rientjes
2011-04-16  1:48           ` Hugh Dickins

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=20110414085535.42559f6b@mfleming-mobl1.ger.corp.intel.com \
    --to=matt@console-pimps.org \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=ieidus@redhat.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=minchan.kim@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.