From: NISHIGUCHI Naoki <nisiguti@jp.fujitsu.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>, xen-devel@lists.xensource.com
Cc: Ian.Pratt@eu.citrix.com, disheng.su@intel.com
Subject: Re: [RFC][PATCH] scheduler: credit scheduler for client virtualization
Date: Thu, 04 Dec 2008 16:45:15 +0900 [thread overview]
Message-ID: <49378A8B.6080904@jp.fujitsu.com> (raw)
In-Reply-To: <C55BFEE2.1FCA7%keir.fraser@eu.citrix.com>
Thank you for your comment.
I'll try to be suitable for both server and client.
Regards,
Naoki Nishiguchi
Keir Fraser wrote:
> On 03/12/2008 08:54, "NISHIGUCHI Naoki" <nisiguti@jp.fujitsu.com> wrote:
>
>> Please review this patch.
>> Any comments are appreciated.
>
> Don't hack it into the existing sched_credit.c unless you are really sharing
> significant amounts of stuff (which it looks like you aren't?).
> sched_bcredit.c would be a cleaner name if there's no sharing. Is a new
> scheduler necessary -- could the existing credit scheduler be generalised
> with your boost mechanism to be suitable for both client and server?
>
> The issue with multiple schedulers is that it's most likely the non-default
> will not be tested, used or maintained. The default credit scheduler gets
> little enough love as it is, and it's really the only sensible scheduler to
> choose now (SEDF is not great -- good example of a rotten non-default
> scheduler).
>
> -- Keir
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2008-12-04 7:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 8:54 [RFC][PATCH] scheduler: credit scheduler for client virtualization NISHIGUCHI Naoki
2008-12-03 9:16 ` Keir Fraser
2008-12-03 12:46 ` George Dunlap
2008-12-04 7:51 ` NISHIGUCHI Naoki
2008-12-04 12:21 ` George Dunlap
2008-12-04 12:37 ` George Dunlap
2008-12-05 3:17 ` NISHIGUCHI Naoki
2008-12-18 2:49 ` NISHIGUCHI Naoki
2008-12-18 10:21 ` George Dunlap
2008-12-05 2:47 ` NISHIGUCHI Naoki
2008-12-05 11:37 ` George Dunlap
2008-12-08 8:37 ` NISHIGUCHI Naoki
2008-12-04 7:45 ` NISHIGUCHI Naoki [this message]
[not found] ` <de76405a0901191232k19d910d5o77160fa5ee7bf06c@mail.gmail.com>
[not found] ` <de76405a0901191257p3b45304fi538d040b5634de23@mail.gmail.com>
[not found] ` <49768FDB.60609@jp.fujitsu.com>
2009-01-21 10:35 ` George Dunlap
2009-01-22 6:15 ` NISHIGUCHI Naoki
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=49378A8B.6080904@jp.fujitsu.com \
--to=nisiguti@jp.fujitsu.com \
--cc=Ian.Pratt@eu.citrix.com \
--cc=disheng.su@intel.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.