public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
	Michel Lespinasse <walken@google.com>,
	linux-mm <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Divyesh Shah <dpshah@google.com>
Subject: Re: FYI: mmap_sem OOM patch
Date: Thu,  8 Jul 2010 10:11:10 +0900 (JST)	[thread overview]
Message-ID: <20100708100836.CD1A.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20100708084005.CD0F.A69D9226@jp.fujitsu.com>

> Yup.
> If admins want to kill memory hogging process manually when the system
> is under heavy swap thrashing, we will face the same problem, need 
> unfairness and fast exit. So, unfair exiting design looks very good.
> 
> If you will updated the description, I'm glad :)

I have one more topic. can we check fatal_signal_pending() instead TIF_MEMDIE?
As I said, if the process received SIGKILL, do the fork/exec/brk/mmap 
starvations have any problem?

Thanks.



  reply	other threads:[~2010-07-08  1:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 23:11 FYI: mmap_sem OOM patch Michel Lespinasse
2010-07-08  0:16 ` KOSAKI Motohiro
2010-07-08  1:11   ` KOSAKI Motohiro [this message]
2010-07-08  9:02 ` Peter Zijlstra
2010-07-08  9:24   ` KOSAKI Motohiro
2010-07-08  9:35     ` Peter Zijlstra
2010-07-08  9:51       ` KOSAKI Motohiro
2010-07-08 10:30 ` Peter Zijlstra
     [not found]   ` <AANLkTimLSnNot2byTWYuIHE8rhGLXbl1zKsQQhmci1Do@mail.gmail.com>
2010-07-08 10:49     ` Peter Zijlstra
2010-07-08 10:57       ` KOSAKI Motohiro
2010-07-08 11:02         ` Peter Zijlstra
2010-07-08 11:06           ` KOSAKI Motohiro
2010-07-08 11:23             ` Peter Zijlstra
2010-07-09  1:31               ` KOSAKI Motohiro
2010-07-12 21:47             ` David Rientjes
2010-07-13  0:14               ` KOSAKI Motohiro
2010-07-13 21:08                 ` David Rientjes
     [not found]         ` <AANLkTimArLPHrxHNEejiXKNYk9To6qsjglbgzyypXP-c@mail.gmail.com>
2010-07-08 12:43           ` Peter Zijlstra

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=20100708100836.CD1A.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=dpshah@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=walken@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