From: Peter Zijlstra <peterz@infradead.org>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
David Woodhouse <dwmw2@infradead.org>,
David Miller <davem@davemloft.net>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [RFC] Static/Runtime CPU/IO bound scheduling polices based on CPU(s) to support complete spectrum of tasks
Date: Thu, 09 Apr 2009 13:38:19 +0200 [thread overview]
Message-ID: <1239277099.7647.345.camel@twins> (raw)
In-Reply-To: <1239272776.3028.11.camel@ht.satnam>
On Thu, 2009-04-09 at 15:56 +0530, Jaswinder Singh Rajput wrote:
> On Tue, 2009-04-07 at 17:02 +0530, Jaswinder Singh Rajput wrote:
> > On Tue, 2009-04-07 at 12:58 +0200, Andi Kleen wrote:
> > > On Tue, Apr 07, 2009 at 03:55:31PM +0530, Jaswinder Singh Rajput wrote:
> > > > I am planning to prepare the followings:
> > >
> > > This seems all quite vague. Perhaps it would be good if you started
> > > with a clear definition what problem you're trying to solve.
> > >
> >
>
> I do not surprise, if this approach seems vague to many developers
> because this is many years ahead of time.
Yes, or not.
For partitioning we have cpusets, for scheduler policies we have
sched_setscheduler().
The only thing we do not have are deadline schedulers, but people are
working on that -- its a rather complex piece of work.
The rest of you babbling is hand-waving about heuristics.
next prev parent reply other threads:[~2009-04-09 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 10:25 [RFC] Static/Runtime CPU/IO bound scheduling polices based on CPU(s) to support complete spectrum of tasks Jaswinder Singh Rajput
2009-04-07 10:58 ` Andi Kleen
2009-04-07 11:32 ` Jaswinder Singh Rajput
2009-04-09 10:26 ` Jaswinder Singh Rajput
2009-04-09 11:38 ` Peter Zijlstra [this message]
2009-04-09 12:02 ` Jaswinder Singh Rajput
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=1239277099.7647.345.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=hpa@kernel.org \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox