public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: luis6674@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to disable group scheduler correctly?
Date: Sun, 27 Jul 2008 19:24:25 -0400	[thread overview]
Message-ID: <488D03A9.4020103@tmr.com> (raw)
In-Reply-To: <842240.12654.qm@web53310.mail.re2.yahoo.com>

Alberto Gonzalez wrote:
> Hello,
> 
> Could anyone tell me which options to enable/disable to have the scheduler behavior as it was before 2.6.25 (i.e, completely disable the group scheduler)? There seems to be a lot of confusion [1] about which options to set or not set, so it would be nice if anyone could give the exact ones.
> 
> Thanks.
> 
> [1] For example, in Arch Linux the group scheduler was first enabled in 2.6.25, but due to latency issues it was quickly disabled. But after that, the following report claims to have problems with everything *GROUP* disabled and that you need to enable CGROUPS to solve them (the report links to similar reports on Gentoo and Ubuntu, so it seems the confusion is quite general):
> 
> http://bugs.archlinux.org/task/10512
> 
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.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  parent reply	other threads:[~2008-07-27 23:16 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 [this message]
2008-07-28 16:47   ` Paul Menage
2008-07-28 17:28     ` Bill Davidsen
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=488D03A9.4020103@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis6674@yahoo.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