From: Avi Kivity <avi@redhat.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCHv3 3/4] qemu-kvm: vhost-net implementation
Date: Sun, 23 Aug 2009 12:58:06 +0300 [thread overview]
Message-ID: <4A9112AE.4070402@redhat.com> (raw)
In-Reply-To: <1250791027.3080.130.camel@blaa>
On 08/20/2009 08:57 PM, Mark McLoughlin wrote:
> - I think /dev/vhost makes more sense - we shouldn't need to add
> another character device if we implement kernel backends for other
> virtio devices
>
I'm of the opposite opinion - vhost-net and vhost-blk are related, but
they're a lot more different than they are similar.
> - I'd really like vhost to support a 'tap' mode, so that we can still
> use a bridge if a NIC isn't available to be assigned. It would
> result in this stuff getting much more testing. Options I see:
>
> 1) Add tap-like functionality to vhost
> 2) Add VHOST_NET_SET_TAP
> 3) Just tell people to set up a tap and bind a raw socket too it
>
> IMHO, (2) makes the most sense - it should be much less exta kernel
> code than (1), and it would be much more convenient than (3)
>
What about connecting vhost-net to one end of a veth pair, and
conencting the other end to a bridge?
> - Distros will also need some way to have the module loaded if its
> not built-in; best I can think of in Fedora is to stick it in
> /etc/sysconfig/modules/kvm.modules
>
> What would be nicer is if loading the kvm module could cause vhost
> to be loaded. It's nice that vhost can be used without kvm, but I
> think if kvm is loaded it's just very convenient to load vhost too.
> See also the problems we've cause with needing mkinitrd/dracut
> hacks by not having KVM_GUEST require VIRTIO_PCI
>
Given that new userspace and a new kernel is needed, I don't see an
issue with the /etc/sysconfig fix.
>> 2. disable tso, gso, lro, jumbo frames on the card
>> (disabling lro + jumbo frames should be sufficient,
>> haven't tested this)
>>
> And this.
>
> If we leave that up to the user or the management app, we need to expose
> to them what features vhost supports so that they can know in future to
> stop disabling them.
>
I imagine the merged version will support all those goodies.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-23 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1250512448.git.mst@redhat.com>
2009-08-17 12:37 ` [PATCHv3 1/4] qemu-kvm: move virtio-pci.o to near pci.o Michael S. Tsirkin
2009-08-17 12:37 ` [PATCHv3 2/4] virtio: move features to an inline function Michael S. Tsirkin
2009-08-17 12:37 ` [PATCHv3 3/4] qemu-kvm: vhost-net implementation Michael S. Tsirkin
2009-08-20 17:57 ` Mark McLoughlin
2009-08-20 18:14 ` Arnd Bergmann
2009-08-20 18:27 ` Michael S. Tsirkin
2009-08-23 9:58 ` Avi Kivity [this message]
2009-08-17 12:37 ` [PATCHv3 4/4] qemu-kvm: add compat eventfd 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=4A9112AE.4070402@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mst@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).