From: Shailabh Nagar <nagar@watson.ibm.com>
To: "Marc E. Fiuczynski" <mef@CS.Princeton.EDU>
Cc: Peter Williams <pwil3058@bigpond.net.au>,
lkml <linux-kernel@vger.kernel.org>,
ckrm-tech <ckrm-tech@lists.sourceforge.net>
Subject: Re: [ckrm-tech] RE: [ANNOUNCE][RFC] plugsched-2.0 patches ...
Date: Fri, 21 Jan 2005 10:16:13 -0500 [thread overview]
Message-ID: <41F11CBD.1030105@watson.ibm.com> (raw)
In-Reply-To: <NIBBJLJFDHPDIBEEKKLPMEODDHAA.mef@cs.princeton.edu>
Marc E. Fiuczynski wrote:
> Hi Peter,
>
>
>>I'm hoping that the CKRM folks will send me a patch to add their
>>scheduler to plugsched :-)
>
>
> They are planning to release a patch against 2.6.10. But their patch wont
> stand alone against 2.6.10 and so it might be difficult for you to integrate
> their code into a scheduler for plugsched.
Thats true. The current CKRM CPU scheduler is not a standalone
component...if it were made one, it would need a non-CKRM interface to
define classes, set their shares etc.
However, we have not investigated the possibility of making our CPU
scheduler a pluggable one that could be loaded into a kernel equipped
with the plugsched patches AND the CKRM framework. This should be
possible but not a high priority until there is more consensus for
having CPU schedulers pluggable at all (we have more basic stuff to fix
in our scheduler such as load balancing).
Of course, we're more than happpy to work with someone willing to chip
in and make our scheduler pluggable.
-- Shailabh
> Also, the CKRM scheduler only modifies Ingo's O(1) scheduler. It certainly
> would be interesting to have CKRM variants of the other schedulers. This
> points to a whole new level of 'plugsched' in that general O(1) schedulers
> need to support fair share plugins.
>
> Marc
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> ckrm-tech mailing list
> https://lists.sourceforge.net/lists/listinfo/ckrm-tech
>
prev parent reply other threads:[~2005-01-21 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 1:23 [ANNOUNCE][RFC] plugsched-2.0 patches Peter Williams
2005-01-20 1:58 ` Kasper Sandberg
2005-01-20 16:14 ` Marc E. Fiuczynski
2005-01-20 17:51 ` Valdis.Kletnieks
2005-01-21 14:11 ` Jens Axboe
2005-01-21 16:29 ` Marc E. Fiuczynski
2005-01-21 16:43 ` Con Kolivas
2005-01-21 21:20 ` Peter Williams
2005-01-21 2:38 ` Peter Williams
2005-01-21 2:50 ` Marc E. Fiuczynski
2005-01-21 15:16 ` Shailabh Nagar [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=41F11CBD.1030105@watson.ibm.com \
--to=nagar@watson.ibm.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mef@CS.Princeton.EDU \
--cc=pwil3058@bigpond.net.au \
/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;
as well as URLs for NNTP newsgroup(s).