From: Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>
To: Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [announce] KVM/NET, paravirtual network device
Date: Thu, 11 Jan 2007 02:38:51 +0100 [thread overview]
Message-ID: <20070111013851.GA11324@elte.hu> (raw)
In-Reply-To: <1168478834.19646.230.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
* Rusty Russell <rusty-8n+1lVoiYb80n/F98K4Iww@public.gmane.org> wrote:
> On Thu, 2007-01-11 at 01:10 +0100, Ingo Molnar wrote:
> > here's a quick update wrt. the KVM paravirtualization work: i'm
> > currently working on KVM/NET, which is a Linux<->Linux virtual network
> > device driver between the KVM host and the KVM guest. It uses the new
> > KVM-paravirtualization infrastructure that i've sent to this list
> > yesterday.
> >
> > while the code is still a prototype, it's working already and here are
> > some early TCP bandwidth (bw_tcp from guest to host) performance results
> > which i'm sure you'll enjoy:
>
> I assume you use kernel support in the host as well? This is exactly
> the code we should share, IMHO; Xen already has such a thing, and I'd
> prefer not to have three implementations in the kernel....
>
> Patches?
no patches yet - it's still prototype. I hope to have something to look
at tomorrow-ish. With lhype sharing ought to be possible, while Xen's
model is quite different. I agree that we dont want 3 implementations in
the kernel ...
Ingo
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2007-01-11 1:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 0:10 [announce] KVM/NET, paravirtual network device Ingo Molnar
[not found] ` <20070111001010.GA28779-X9Un+BFzKDI@public.gmane.org>
2007-01-11 1:27 ` Rusty Russell
[not found] ` <1168478834.19646.230.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-01-11 1:38 ` Ingo Molnar [this message]
2007-01-11 9:57 ` Dor Laor
2007-01-11 8:21 ` Avi Kivity
[not found] ` <45A5F382.7050207-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-01-11 17:39 ` Andy Ross
[not found] ` <45A67653.9000406-DKCljQvcl/LNLxjTenLetw@public.gmane.org>
2007-01-11 17:49 ` Avi Kivity
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=20070111013851.GA11324@elte.hu \
--to=mingo-x9un+bfzkdi@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=rusty-8n+1lVoiYb80n/F98K4Iww@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 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.