From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Dhaval Giani <dhaval@linux.vnet.ibm.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
Balbir Singh <balbir@in.ibm.com>,
Aneesh Kumar KV <aneesh.kumar@linux.vnet.ibm.com>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: don't allow rt_runtime_us to be zero for groups having rt tasks
Date: Wed, 27 Feb 2008 16:08:39 +0100 [thread overview]
Message-ID: <1204124919.6242.408.camel@lappy> (raw)
In-Reply-To: <20080227150350.GB21610@elte.hu>
On Wed, 2008-02-27 at 16:03 +0100, Ingo Molnar wrote:
> * Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>
> >
> > On Wed, 2008-02-27 at 18:54 +0530, Dhaval Giani wrote:
> >
> > > This patch checks if we can set the rt_runtime_us to 0. If there is a
> > > realtime task in the group, we don't want to set the rt_runtime_us as 0
> > > or bad things will happen.
> > >
> > > Signed-off-by: Dhaval Giani <dhaval@linux.vnet.ibm.com>
> >
> > Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
>
> doesnt apply to sched-devel.git - what's the plan here?
stick in front, drop the other two sched-rt-group patches for which I'll
send you an update somewhere today.
These two patches would be candidates to push to linus..
next prev parent reply other threads:[~2008-02-27 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 11:08 [PATCH] sched: don't allow rt_runtime_us to be zero for groups having rt tasks Dhaval Giani
2008-02-27 12:46 ` Peter Zijlstra
2008-02-27 13:24 ` Dhaval Giani
2008-02-27 13:40 ` Peter Zijlstra
2008-02-27 14:11 ` Peter Zijlstra
2008-02-27 15:03 ` Ingo Molnar
2008-02-27 15:08 ` Peter Zijlstra [this message]
2008-02-27 15:10 ` Dhaval Giani
2008-02-27 21:47 ` Peter Zijlstra
2008-02-28 9:51 ` Dhaval Giani
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=1204124919.6242.408.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=balbir@in.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=skumar@linux.vnet.ibm.com \
--cc=vatsa@linux.vnet.ibm.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 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.