From: Ingo Molnar <mingo@elte.hu>
To: Parag Warudkar <parag.warudkar@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"akpm@osdl.org" <akpm@osdl.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED
Date: Sun, 4 May 2008 11:24:17 +0200 [thread overview]
Message-ID: <20080504092417.GA3425@elte.hu> (raw)
In-Reply-To: <82e4877d0805031742o464dd581wd93173d79705ce0d@mail.gmail.com>
* Parag Warudkar <parag.warudkar@gmail.com> wrote:
> GROUP_SCHED is confirmed to cause unacceptable latencies -
> http://lkml.org/lkml/2008/5/2/370.
fixes for that are queued up in sched-devel:
http://people.redhat.com/mingo/sched-devel.git/README
could you test whether that works any better for you?
Ingo
next prev parent reply other threads:[~2008-05-04 9:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 0:42 [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED Parag Warudkar
2008-05-04 9:24 ` Ingo Molnar [this message]
2008-05-05 15:14 ` Parag Warudkar
2008-05-05 17:15 ` Ingo Molnar
2008-05-05 18:24 ` Sam Ravnborg
2008-05-05 18:36 ` Sergio Luis
2008-05-05 18:45 ` Ingo Molnar
2008-05-05 19:49 ` [PATCH] kconfig: add support for stdin (make K=- ...) Sam Ravnborg
2008-05-06 3:51 ` Oleg Verych
2008-05-05 19:05 ` [PATCH] default to n for GROUP_SCHED and FAIR_GROUP_SCHED Sam Ravnborg
2008-05-05 18:42 ` Ingo Molnar
2008-05-05 19:01 ` Sam Ravnborg
2008-05-05 19:56 ` Arjan van de Ven
2008-05-05 20:27 ` Ingo Molnar
2008-05-05 20:48 ` Linus Torvalds
2008-05-05 21:05 ` Ingo Molnar
2008-05-05 21:40 ` Parag Warudkar
2008-05-25 19:30 ` Roman Zippel
2008-05-05 17:21 ` Ingo Molnar
2008-05-05 17:33 ` Jesse Barnes
2008-05-05 18:36 ` Ingo Molnar
2008-05-05 21:36 ` Parag Warudkar
2008-05-05 21:49 ` Ingo Molnar
2008-05-06 0:38 ` Ingo Molnar
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=20080504092417.GA3425@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
--cc=peterz@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.