From: Dor Laor <dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: vast yellow <vastyellow-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: when to relize the Paravirtualized networking ?
Date: Wed, 03 Oct 2007 01:18:23 +0200 [thread overview]
Message-ID: <4702D1BF.1040109@qumranet.com> (raw)
In-Reply-To: <cc9017b10710021610i67973570w82e2be0197a064d6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 612 bytes --]
vast yellow wrote:
>
> Anyone know when to release include the following features
>
> # Paravirtualized networking
I have such a code in a separate git repository. It is not yet
production ready.
The next release is a rebase of Rusty code for virtio and some KVM/Qemu
backend.
It probably be ready in few weeks.
> # Paravirtualized block device
The effort is not big since Rusty has paved most of the way.
Some qemu block handling needs to be done. Again it can happen in 1-2
months.
> KVM Tap network is slower than Xen. Can we optimize it?
>
Are you talking about PV driver or fully virtualized nic?
Dor.
[-- Attachment #1.2: Type: text/html, Size: 1353 bytes --]
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #3: Type: text/plain, Size: 186 bytes --]
_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel
next prev parent reply other threads:[~2007-10-02 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 23:10 when to relize the Paravirtualized networking ? vast yellow
[not found] ` <cc9017b10710021610i67973570w82e2be0197a064d6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-02 23:18 ` Dor Laor [this message]
[not found] ` <4702D1BF.1040109-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-03 7:36 ` vast yellow
[not found] ` <cc9017b10710030036t735953fped9fd4a0a0ad3d54-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-05 23:55 ` Dor Laor
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=4702D1BF.1040109@qumranet.com \
--to=dor.laor-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=vastyellow-Re5JQEeQqe8AvxtiuMwx3w@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