From: Bill Davidsen <davidsen@tmr.com>
To: Paul Menage <menage@google.com>
Cc: luis6674@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: How to disable group scheduler correctly?
Date: Mon, 28 Jul 2008 13:28:42 -0400 [thread overview]
Message-ID: <488E01CA.7000302@tmr.com> (raw)
In-Reply-To: <6599ad830807280947j21fda44ajd51ce1dd523d9472@mail.gmail.com>
Paul Menage wrote:
> On Sun, Jul 27, 2008 at 4:24 PM, Bill Davidsen <davidsen@tmr.com> wrote:
>
>> Would be nice to have a clean way to do this at runtime, so you could run a
>> distribution kernel and just avoid the group part of the scheduling.
>>
>
> If the cgroups scheduler is enabled but you don't actually create any
> cpu scheduler cgroups, then you're just scheduling across a single
> group that contains all processes/threads. Is that distinguishable
> from not having group scheduling at all?
>
In decisions, hopefully not. But given that there are other places in
kernel which allow code to be bypassed completely, a flag which would
simply avoid ever going into the code would not be a new idea. In the
network code there are flags to prevent passing packets in a bridge
through iptables, something similar could be provided in scheduling. It
actually makes sense to default the flag to "no cgroups" asnd only
enable it if cgroups have been defined.
There is no optimization faster than not executing the code.
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
next prev parent reply other threads:[~2008-07-28 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 17:05 How to disable group scheduler correctly? Alberto Gonzalez
2008-07-25 17:38 ` Dhaval Giani
2008-07-27 23:24 ` Bill Davidsen
2008-07-28 16:47 ` Paul Menage
2008-07-28 17:28 ` Bill Davidsen [this message]
2008-07-28 16:42 ` Chris Friesen
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=488E01CA.7000302@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis6674@yahoo.com \
--cc=menage@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