From: Avi Kivity <avi@redhat.com>
To: alex <tomorrowanewday@gmail.com>
Cc: Andrew Theurer <habanero@linux.vnet.ibm.com>,
anthony@codemonkey.ws, kvm@vger.kernel.org, mingo@elte.hu
Subject: Re: patch for virtual machine oriented scheduling(1)
Date: Sun, 26 Apr 2009 12:48:10 +0300 [thread overview]
Message-ID: <49F42DDA.6040308@redhat.com> (raw)
In-Reply-To: <820ac2e90904231624l6e5f177wbbdef8b58ed96d4a@mail.gmail.com>
alex wrote:
>> Just wondering, was it not possible to introduce a new scheduling class in
>> the current scheduler? My impression was that the current scheduler was
>> fairly modular and should allow this.
>>
>> -Andrew
>>
> The reasons are:
> 1. I am afraid that modifications to the Linux scheduler might cause
> unexpected effects, because it is a global one.
>
True, extra care is needed.
> 2. an extra execution control solution like mine is the simplest one
> to implement.
>
But it results in an overall more complex system.
> 3. As far as I can see, the benefit of replacing Linux scheduler only
> lies that as soon as a scheduling decision is made, it can be put into
> practice immediately. I think this benefit is neglectable.
>
It also make maintenance easier, and brings the benefits to ordinary
(non-kvm) processes.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-04-26 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 14:49 patch for virtual machine oriented scheduling(1) alex
2009-04-23 16:18 ` Andrew Theurer
2009-04-23 23:24 ` alex
2009-04-26 9:48 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-23 2:39 alex
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=49F42DDA.6040308@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=habanero@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tomorrowanewday@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox