From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Chris Wright <chrisw@sous-sol.org>,
Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.linux-foundation.org, "Xin,
Xiaohui" <xiaohui.xin@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"hpa@zytor.com" <hpa@zytor.com>, "mingo@elte.hu" <mingo@elte.hu>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [RFC] Virtual Machine Device Queues(VMDq) support on KVM
Date: Tue, 22 Sep 2009 20:34:28 +0200 [thread overview]
Message-ID: <200909222034.28865.arnd@arndb.de> (raw)
In-Reply-To: <20090922092957.17e68cbc@s6510>
On Tuesday 22 September 2009, Stephen Hemminger wrote:
> > My idea for that was to open multiple file descriptors to the same
> > macvtap device and let the kernel figure out the right thing to
> > do with that. You can do the same with raw packed sockets in case
> > of vhost_net, but I wouldn't want to add more complexity to the
> > tun/tap driver for this.
> >
> Or get tap out of the way entirely. The packets should not have
> to go out to user space at all (see veth)
How does veth relate to that, do you mean vhost_net? With vhost_net,
you could still open multiple sockets, only the access is in the kernel.
Obviously, once it all is in the kernel, that could be done under the
covers, but I think it would be cleaner to treat vhost_net purely as
a way to bypass the syscalls for user space, with as little as possible
visible impact otherwise.
Arnd <><
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Chris Wright <chrisw@sous-sol.org>,
Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.linux-foundation.org, "Xin,
Xiaohui" <xiaohui.xin@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"hpa@zytor.com" <hpa@zytor.com>, "mingo@elte.hu" <mingo@elte.hu>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [RFC] Virtual Machine Device Queues(VMDq) support on KVM
Date: Tue, 22 Sep 2009 20:34:28 +0200 [thread overview]
Message-ID: <200909222034.28865.arnd@arndb.de> (raw)
In-Reply-To: <20090922092957.17e68cbc@s6510>
On Tuesday 22 September 2009, Stephen Hemminger wrote:
> > My idea for that was to open multiple file descriptors to the same
> > macvtap device and let the kernel figure out the right thing to
> > do with that. You can do the same with raw packed sockets in case
> > of vhost_net, but I wouldn't want to add more complexity to the
> > tun/tap driver for this.
> >
> Or get tap out of the way entirely. The packets should not have
> to go out to user space at all (see veth)
How does veth relate to that, do you mean vhost_net? With vhost_net,
you could still open multiple sockets, only the access is in the kernel.
Obviously, once it all is in the kernel, that could be done under the
covers, but I think it would be cleaner to treat vhost_net purely as
a way to bypass the syscalls for user space, with as little as possible
visible impact otherwise.
Arnd <><
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-09-22 18:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 6:58 [RFC] Virtual Machine Device Queues(VMDq) support on KVM Xin, Xiaohui
2009-09-01 6:58 ` Xin, Xiaohui
2009-09-01 6:58 ` Xin, Xiaohui
2009-09-01 16:05 ` Stephen Hemminger
2009-09-01 16:05 ` Stephen Hemminger
2009-09-02 6:45 ` Xin, Xiaohui
2009-09-02 6:45 ` Xin, Xiaohui
2009-09-02 6:45 ` Xin, Xiaohui
2009-09-21 7:07 ` Rusty Russell
2009-09-21 7:07 ` Rusty Russell
2009-09-21 16:21 ` Stephen Hemminger
2009-09-21 16:21 ` Stephen Hemminger
2009-09-21 16:27 ` Chris Wright
2009-09-21 16:27 ` Chris Wright
2009-09-22 10:38 ` Michael S. Tsirkin
2009-09-22 10:38 ` Michael S. Tsirkin
2009-09-22 11:50 ` Arnd Bergmann
2009-09-22 11:50 ` Arnd Bergmann
2009-09-22 11:50 ` Arnd Bergmann
2009-09-22 16:29 ` Stephen Hemminger
2009-09-22 16:29 ` Stephen Hemminger
2009-09-22 18:34 ` Arnd Bergmann [this message]
2009-09-22 18:34 ` Arnd Bergmann
2009-09-22 18:34 ` Arnd Bergmann
2009-09-22 16:29 ` Stephen Hemminger
2009-09-22 10:38 ` Michael S. Tsirkin
2009-09-21 16:27 ` Chris Wright
2009-09-21 16:21 ` Stephen Hemminger
2009-09-21 7:07 ` Rusty Russell
2009-09-01 16:05 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2009-09-01 6:58 Xin, Xiaohui
2009-09-01 6:58 Xin, Xiaohui
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=200909222034.28865.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@vyatta.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xiaohui.xin@intel.com \
/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.