LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Dmitry Adamushko <dmitry.adamushko@gmail.com>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [Regression] 2.6.24-git9: RT sched mishandles artswrapper (bisected)
Date: Wed, 6 Feb 2008 23:18:27 +0100	[thread overview]
Message-ID: <200802062318.28172.rjw@sisk.pl> (raw)
In-Reply-To: <1202335261.6274.11.camel@lappy>

On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
> 
> On Wed, 2008-02-06 at 22:50 +0100, Rafael J. Wysocki wrote:
> > On Wednesday, 6 of February 2008, Peter Zijlstra wrote:
> 
> > > Well, that whole queue.
> > 
> > It doesn't compile for me.
> 
> I did solve some compile issues since posting, Ingo should have the
> compiling version in sched-devel soonish (don't know if he pushed it
> already).

Can you point me to the cleaned up version, please?

> > > Your test program just failed to obtain realtime scheduling
> > 
> > Well, it shouldn't.  The expected result is to obtain realtime scheduling
> > or we will break existing setups.
> 
> Thats a case of wrong expectations in my book. You enabled group
> scheduling and hence behaviour changes.

So, I'd have to unset FAIR_GROUP_SCHED to obtain the previous behavior?

> There is just nothing much one can do about it, if you don't assign bandwidth
> to a group, it won't be able to run anything. Better to refuse to run, than to sit
> idle, right? 

As a general rule, probably yes.

> But I appreciate the situation, therefore I made the whole rt-group
> scheduling a separate .config option (which defaults to n)

Which is introduced by the new patches, isn't it?

  reply	other threads:[~2008-02-06 22:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01  1:37 Rafael J. Wysocki
2008-02-01  2:04 ` Rafael J. Wysocki
2008-02-01  7:44   ` Peter Zijlstra
2008-02-01  9:50     ` Peter Zijlstra
2008-02-01 11:50       ` Rafael J. Wysocki
2008-02-01 12:09         ` Peter Zijlstra
2008-02-01 23:39           ` Rafael J. Wysocki
2008-02-05 21:46             ` Dmitry Adamushko
2008-02-06  1:21               ` Rafael J. Wysocki
     [not found] ` <b647ffbd0802060040wbfe16afq4355e8f4f31ab06b@mail.gmail.com>
     [not found]   ` <1202288548.19243.47.camel@lappy>
2008-02-06 18:25     ` Rafael J. Wysocki
2008-02-06 21:43       ` Peter Zijlstra
2008-02-06 21:50         ` Rafael J. Wysocki
2008-02-06 22:01           ` Peter Zijlstra
2008-02-06 22:18             ` Rafael J. Wysocki [this message]
2008-02-06 22:34               ` Peter Zijlstra
2008-02-06 23:31                 ` Rafael J. Wysocki
2008-02-06 23:34                   ` Ingo Molnar
2008-02-07 19:53                     ` Rafael J. Wysocki
2008-02-07 21:20                       ` Peter Zijlstra
2008-02-10 12:30                     ` Rafael J. Wysocki

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=200802062318.28172.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=dmitry.adamushko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --subject='Re: [Regression] 2.6.24-git9: RT sched mishandles artswrapper (bisected)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).