From: Ingo Molnar <mingo@elte.hu>
To: Mike Galbraith <efault@gmx.de>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [RFC PATCH] sched: START_NICE feature (temporarily niced forks) (v3)
Date: Wed, 15 Sep 2010 16:02:46 +0200 [thread overview]
Message-ID: <20100915140246.GA25983@elte.hu> (raw)
In-Reply-To: <1284556366.22863.80.camel@marge.simson.net>
* Mike Galbraith <efault@gmx.de> wrote:
> On Wed, 2010-09-15 at 11:22 +0200, Ingo Molnar wrote:
> > * Mike Galbraith <efault@gmx.de> wrote:
> >
> > > Tangent: cgroups with classification user/pgid
> > >
> > > taskset -c 3 ./wakeup-latency& sleep 30 && killall wakeup-latency
> > > (taskset -c 3 make -j10 running)
> > >
> > > maximum latency: 256.5 µs
> > > average latency: 25.7 µs
> > > missed timer events: 0
> > >
> > > Rather spiffy for this case.
> >
> > Ouch, nothing beats proper segregation of workloads.
> >
> > It would be _really_ nice to get that automatically somehow, for make -j
> > jobs. Perhaps a per tty auto-cgroup-classification kernel feature?
> >
> > We cannot really rely on distros to pull this off.
>
> Dunno, wasn't hard.
Renicing a make -j 10 isnt hard either - still people/apps dont do it
:-/
Thanks,
Ingo
next prev parent reply other threads:[~2010-09-15 14:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 20:25 Mathieu Desnoyers
2010-09-15 8:37 ` Mike Galbraith
2010-09-15 9:03 ` Mike Galbraith
2010-09-15 9:22 ` Ingo Molnar
2010-09-15 13:12 ` Mike Galbraith
2010-09-15 14:02 ` Ingo Molnar [this message]
2010-09-16 10:30 ` Mike Galbraith
2010-09-20 11:43 ` Peter Zijlstra
2010-09-20 16:02 ` Mathieu Desnoyers
2010-09-20 16:15 ` Peter Zijlstra
2010-09-20 18:49 ` Mathieu Desnoyers
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=20100915140246.GA25983@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tony@atomide.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
Powered by JetHome