From: Karim Yaghmour <karim@opersys.com>
To: Rik van Riel <riel@redhat.com>
Cc: Nuno Silva <nuno.silva@vgertech.com>,
JustFillBug <mozbugbox@yahoo.com.au>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Cooperative Linux
Date: Mon, 26 Jan 2004 10:20:31 -0500 [thread overview]
Message-ID: <4015303F.1030003@opersys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401260633280.26321-100000@chimarrao.boston.redhat.com>
Rik van Riel wrote:
>>So, for example, Xen assumes that all OSes are going to use the same
>>devices for I/O: same disk, same NIC, etc. It therefore implements lots
>>of virtual devices for these.
>
>
> Consolidation means more efficient hardware use ...
In the case of a UP system, it may ... depending on what you're
trying to do. On an SMP system or an SMP-cluster, however,
consilidation is likely to mean loss of performance.
>>Wouldn't it be just better to reuse the existing work on the hotplug
>>hardware (hotplug CPU, hotplug memory, etc.) to have the kernels
>>get/return hardware resources to the nanokernel?
>
>
> That means a loss of flexibility.
It depends on your setup. In the case of an SMP-cluster where all
OS instances are launched at startup, where runtime setup
modification can be costly because of global table changes, and
where centralization is to be avoided in as much as possible, then
the hotplug capabilities are probably the best way to go. If there's
a desire to have both capabilities (fine-grain allocation and
gross-grain allocation) in whatever is finally adopted, then that's
something to keep in mind. I guess I'm just saying that there are pros
and cons, depending on your setup.
> Furthermore, these hotplug
> patches don't seem ready yet.
Yes, I'm aware of this. There are other components of a truely
generic virtualization interface which are missing. Does that mean
we shouldn't think ahead?
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
next prev parent reply other threads:[~2004-01-26 15:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 19:35 [ANNOUNCE] Cooperative Linux Dan Aloni
2004-01-25 20:01 ` Karim Yaghmour
2004-01-26 3:40 ` Nuno Silva
2004-01-26 3:57 ` JustFillBug
2004-01-26 4:59 ` Ben Pfaff
2004-01-26 9:19 ` Christoph Hellwig
2004-01-26 17:00 ` Ben Pfaff
2004-01-26 19:44 ` Christoph Hellwig
2004-01-26 20:04 ` Omkhar Arasaratnam
2004-01-26 5:04 ` Karim Yaghmour
2004-01-26 5:06 ` Nuno Silva
2004-01-26 6:36 ` Karim Yaghmour
2004-01-26 11:35 ` Rik van Riel
2004-01-26 15:20 ` Karim Yaghmour [this message]
2004-01-26 11:32 ` Rik van Riel
2004-01-27 0:20 ` David Schwartz
2004-01-26 4:26 ` Dan Aloni
2004-01-26 5:01 ` Karim Yaghmour
2004-01-26 7:23 ` Dan Aloni
-- strict thread matches above, loose matches on Subject: below --
2004-01-29 5:57 Paul Zimmerman
2004-01-29 9:10 ` Dan Aloni
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=4015303F.1030003@opersys.com \
--to=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mozbugbox@yahoo.com.au \
--cc=nuno.silva@vgertech.com \
--cc=riel@redhat.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