From: "Michael S. Tsirkin" <mst@redhat.com>
To: anthony@codemonkey.ws, virtualization@lists.linux-foundation.org,
kvm@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>
Subject: vhost-net todo list
Date: Wed, 16 Sep 2009 13:04:38 +0300 [thread overview]
Message-ID: <20090916100438.GA30036@redhat.com> (raw)
Some people asked about getting involved with vhost.
Here's a short list of projects.
vhost-net driver projects
- profiling would be very helpful, I have not done any yet
- tap support - working on it now
- merged buffers - working on it now
- scalability/fairness for large # of guests - working on it now
- logging support with dirty page tracking in kernel - working on it now
- indirect buffers - worth it?
- vm exit mitigation for TX (worth it?
naive implementation does not seem to help)
- interrupt mitigation for RX
- level triggered interrupts - what's the best thing
to do here?
qemu projects
- migration support
- level triggered interrupts - what's the best thing
to do here?
- upstream support for injecting interrupts from kernel,
from qemu-kvm.git to qemu.git
(this is a vhost dependency, without it vhost
can't be upstreamed, or it can, but without real benefit)
- general cleanup and upstreaming
projects involing networking stack
- export socket from tap so vhost can use it - working on it now
- extend raw sockets to support GSO/checksum offloading,
and teach vhost to use that capability
[one way to do this: virtio net header support]
will allow working with e.g. macvlan
long term projects
- multiqueue (involves all of vhost, qemu, virtio,
networking stack)
- More testing is always good
--
MST
next reply other threads:[~2009-09-16 10:06 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 10:04 Michael S. Tsirkin [this message]
2009-09-16 14:52 ` vhost-net todo list Arnd Bergmann
2009-09-16 14:58 ` Michael S. Tsirkin
2009-09-16 15:08 ` Arnd Bergmann
2009-09-16 15:19 ` Michael S. Tsirkin
2009-09-16 15:27 ` Arnd Bergmann
2009-09-16 15:46 ` GDB + KVM Debug Saksena, Abhishek
2009-09-16 16:02 ` Jan Kiszka
2009-09-16 16:24 ` Saksena, Abhishek
2009-09-16 16:37 ` Jan Kiszka
2009-09-16 17:15 ` Avi Kivity
2009-09-16 17:56 ` Jan Kiszka
2009-09-16 18:26 ` Avi Kivity
2009-09-16 18:49 ` Saksena, Abhishek
2009-09-17 8:35 ` Jan Kiszka
2009-10-20 18:48 ` Saksena, Abhishek
2009-10-23 17:01 ` Jan Kiszka
2009-10-23 16:19 ` GDB Debugging Saksena, Abhishek
2009-10-24 16:44 ` Yolkfull Chow
2009-09-16 16:45 ` vhost-net todo list Michael S. Tsirkin
2009-09-17 11:30 ` Arnd Bergmann
2009-09-17 11:30 ` Arnd Bergmann
2009-09-17 11:47 ` Michael S. Tsirkin
2009-09-17 12:14 ` Arnd Bergmann
2009-09-17 12:25 ` Michael S. Tsirkin
2009-09-17 15:08 ` Arnd Bergmann
2009-09-17 15:08 ` Arnd Bergmann
2009-09-17 12:25 ` Michael S. Tsirkin
2009-09-17 12:14 ` Arnd Bergmann
2009-09-17 11:47 ` Michael S. Tsirkin
2009-09-16 16:45 ` Michael S. Tsirkin
2009-09-16 17:13 ` Avi Kivity
2009-09-16 17:13 ` Avi Kivity
2009-09-16 15:27 ` Arnd Bergmann
2009-09-16 15:19 ` Michael S. Tsirkin
2009-09-16 15:08 ` Arnd Bergmann
2009-09-16 14:58 ` Michael S. Tsirkin
2009-09-16 15:01 ` Michael S. Tsirkin
2009-09-16 15:01 ` Michael S. Tsirkin
2009-09-16 14:52 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2009-09-16 10:04 Michael S. Tsirkin
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=20090916100438.GA30036@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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.