From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Mark Clarkson <mark.clarkson-Sphq+rzYrv710XsdtD+oqA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: White screen
Date: Tue, 19 Dec 2006 13:08:38 +0200 [thread overview]
Message-ID: <4587C836.6050004@qumranet.com> (raw)
In-Reply-To: <1166525624.13369.37.camel@localhost>
Mark Clarkson wrote:
> Unfortunately the slow network performance and the fact that, on my
> setup at least, network io takes 100% of a single core means that kvm is
> not currently useful for server use.
>
>
Certainly, kvm is slow right now for server use. This will improve
quickly though.
> I really like the idea of kvm over Xen as it's a much 'cleaner' solution
> and would dearly love to see paravirtualised network drivers, at least
> for Linux guests, which would allow me to consider moving from Xen to
> kvm.
>
> Do you think it possible/probable for someone with around 10 years
> knowledge of Linux and C programming but with no kernel module writing
> experience to be able to write a paravirtualised network driver for
> linux in under 6 months (in his/her spare time)?
Well, it depends on how much spare time said someone is willing to
commit. This is a fairly complex system. I will provide guidance
however, should anyone require it.
For someone who is familiar with Linux and Windows networking, the task
should take a few weeks.
> Is there any example
> code around for this? Would it be a case of say, modifying an ne2k
> driver?
Certainly that's the easiest way to start, as only the xmit/receive
paths need to be accelerated.
> In fact, I've literally just seen that paravirtualised drivers
> exist for xen for linux 2.6 kernels and I presume these are open source
>
I understand only the Linux guest drivers are open source.
The Xen paravirtualized drivers are quite complex and heavily tied to
Xen (by using Xen features such as grant tables and event channels,
which are all unnecessary for kvm). While we might borrow code from
them, outright sharing is questionable.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-12-19 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 1:49 White screen Mark Clarkson
2006-12-18 8:07 ` Avi Kivity
[not found] ` <45864C31.8080907-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2006-12-18 8:16 ` Dor Laor
2006-12-19 10:53 ` Mark Clarkson
2006-12-19 11:08 ` Avi Kivity [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=4587C836.6050004@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=mark.clarkson-Sphq+rzYrv710XsdtD+oqA@public.gmane.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