From: Mike Galbraith <efault@gmx.de>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Sam Ravnborg <sam@ravnborg.org>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: (ondemand) CPU governor regression between 2.6.23 and 2.6.24
Date: Sun, 27 Jan 2008 19:58:48 +0100 [thread overview]
Message-ID: <1201460328.5092.95.camel@homer.simson.net> (raw)
In-Reply-To: <200801271339.14668.toralf.foerster@gmx.de>
On Sun, 2008-01-27 at 13:39 +0100, Toralf Förster wrote:
> Am Sonntag, 27. Januar 2008 schrieben Sie:
> >
> > On Sun, 2008-01-27 at 12:00 +0100, Toralf Förster wrote:
> > > BTW the dnetc process runs under the user "dnetc" with nice level -19,
> > > my process runs under my own user id "tfoerste" therefore I wouldn't expect
> > > that both processes got the same processor resources isn't it ? :
> >
> > Normal. Nice level controls cpu distribution _within_ a task group,
> > whereas distribution between groups is controlled by cpu_share. It's
> > going to take a while for folks to get used to having two levels of cpu
> > distribution.
>
> Ough, does this mean that for a multi-user scenario of 2 non-root users "A" and
> "B" each running exactly 1 process with nice level 0 and 19 rerspectively
> that both share ~50% of the CPU *and furthermore* that that user "B" does never
> ever have a chance to be nice to user "A" although his process should really
> use only those CPU cycles not eated by any other user ?
Yes. If you want one task group to receive less cpu cycles, you have to
'nice' that task group by reducing it's share.
> If the answer is yes what's about extending the current behaviour to consider
> (optionally) nice level of running processes in the case where
> CONFIG_FAIR_GROUP_SCHED is set ?
I think it's better to just disable fair group scheduling if it doesn't
suit your needs. It's not going to be everyone's cup of tea.
-Mike
next prev parent reply other threads:[~2008-01-27 18:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 17:11 (ondemand) CPU governor regression between 2.6.23 and 2.6.24 Tomasz Chmielewski
2008-01-26 18:46 ` Toralf Förster
2008-01-27 14:46 ` Srivatsa Vaddagiri
2008-01-27 15:06 ` Toralf Förster
2008-01-27 16:54 ` Srivatsa Vaddagiri
2008-01-27 16:57 ` Toralf Förster
2008-01-27 21:27 ` Peter Zijlstra
2008-01-27 22:32 ` Ingo Molnar
2008-01-28 8:38 ` Helge Hafting
2008-01-26 21:38 ` Toralf Förster
2008-01-26 21:45 ` Sam Ravnborg
[not found] ` <200801271200.04971.toralf.foerster@gmx.de>
[not found] ` <1201433167.22060.10.camel@homer.simson.net>
2008-01-27 12:39 ` Toralf Förster
2008-01-27 18:58 ` Mike Galbraith [this message]
2008-01-27 21:14 ` Toralf Förster
2008-01-27 21:25 ` Peter Zijlstra
2008-01-28 13:18 ` Ingo Molnar
2008-01-28 15:16 ` Toralf Förster
-- strict thread matches above, loose matches on Subject: below --
2008-01-26 14:06 Toralf Förster
2008-02-04 0:32 ` Andrew Morton
2008-02-04 0:36 ` Andrew Morton
2008-02-04 17:44 ` Pallipadi, Venkatesh
2008-02-04 19:18 ` Toralf Förster
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=1201460328.5092.95.camel@homer.simson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sam@ravnborg.org \
--cc=toralf.foerster@gmx.de \
/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