From: Jon Masters <jonmasters@gmail.com>
To: Diwaker Gupta <diwakergupta@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hierarchical schedulers
Date: Thu, 14 Oct 2004 00:12:04 +0100 [thread overview]
Message-ID: <35fb2e590410131612c3ee333@mail.gmail.com> (raw)
In-Reply-To: <1b0b45570410131407127df0b3@mail.gmail.com>
On Wed, 13 Oct 2004 14:07:31 -0700, Diwaker Gupta
<diwakergupta@gmail.com> wrote:
> Are there any efforts underway (apart from CKRM -- ckrm.sf.net) to
> provide hierarchical schedulers
In terms of what you're talking about (unified scheduling of various
different resources in to groups), not as far as I'm aware. There are
existing ways of layering things like regular process scheduling in to
groups (scheduling domains, and other similar examples) but what
you're after is different. Someone will doubtlessly crawl out of the
woodwork with examples which do what you want though :-)
Jon.
prev parent reply other threads:[~2004-10-13 23:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 21:07 Hierarchical schedulers Diwaker Gupta
2004-10-13 23:12 ` Jon Masters [this message]
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=35fb2e590410131612c3ee333@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=diwakergupta@gmail.com \
--cc=jonathan@jonmasters.org \
--cc=linux-kernel@vger.kernel.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