From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kosaki.motohiro@jp.fujitsu.com, Andrey Vagin <avagin@openvz.org>,
Minchan Kim <minchan.kim@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"Luis Claudio R. Goncalves" <lclaudio@uudg.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
David Rientjes <rientjes@google.com>,
Oleg Nesterov <oleg@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 2/4] remove boost_dying_task_prio()
Date: Tue, 12 Apr 2011 09:35:16 +0900 (JST) [thread overview]
Message-ID: <20110412093503.43EF.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <20110411145832.ae133cf8.akpm@linux-foundation.org>
Hi
> On Mon, 11 Apr 2011 14:31:18 +0900 (JST)
> KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
>
> > This is a almost revert commit 93b43fa (oom: give the dying
> > task a higher priority).
> >
> > The commit dramatically improve oom killer logic when fork-bomb
> > occur. But, I've found it has nasty corner case. Now cpu cgroup
> > has strange default RT runtime. It's 0! That said, if a process
> > under cpu cgroup promote RT scheduling class, the process never
> > run at all.
>
> hm. How did that happen? I thought that sched_setscheduler() modifies
> only a single thread, and that thread is in the process of exiting?
If admin insert !RT process into a cpu cgroup of setting rtruntime=0,
usually it run perfectly because !RT task isn't affected from rtruntime
knob, but If it promote RT task, by explicit setscheduler() syscall or
OOM, the task can't run at all.
In short, now oom killer don't work at all if admin are using cpu
cgroup and don't touch rtruntime knob.
next prev parent reply other threads:[~2011-04-12 0:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110411142949.006C.A69D9226@jp.fujitsu.com>
[not found] ` <20110411143128.0070.A69D9226@jp.fujitsu.com>
2011-04-11 21:53 ` [PATCH 1/4] vmscan: all_unreclaimable() use zone->all_unreclaimable as a name Andrew Morton
2011-04-12 1:04 ` KOSAKI Motohiro
2011-04-12 1:26 ` Andrew Morton
2011-04-12 10:55 ` KOSAKI Motohiro
2011-04-13 18:48 ` David Rientjes
[not found] ` <20110411143215.0074.A69D9226@jp.fujitsu.com>
2011-04-11 21:58 ` [PATCH 2/4] remove boost_dying_task_prio() Andrew Morton
2011-04-12 0:35 ` KOSAKI Motohiro [this message]
2011-04-13 18:41 ` 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=20110412093503.43EF.A69D9226@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=avagin@openvz.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lclaudio@uudg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=oleg@redhat.com \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®