From: "Michael S. Tsirkin" <mst@redhat.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
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 13:38:07 +0300 [thread overview]
Message-ID: <20090922103807.GA2555@redhat.com> (raw)
In-Reply-To: <20090921162718.GM26034@sequoia.sous-sol.org>
On Mon, Sep 21, 2009 at 09:27:18AM -0700, Chris Wright wrote:
> * Stephen Hemminger (shemminger@vyatta.com) wrote:
> > On Mon, 21 Sep 2009 16:37:22 +0930
> > Rusty Russell <rusty@rustcorp.com.au> wrote:
> >
> > > > > Actually this framework can apply to traditional network adapters which have
> > > > > just one tx/rx queue pair. And applications using the same user/kernel interface
> > > > > can utilize this framework to send/receive network traffic directly thru a tx/rx
> > > > > queue pair in a network adapter.
> > > > >
> >
> > More importantly, when virtualizations is used with multi-queue
> > NIC's the virtio-net NIC is a single CPU bottleneck. The virtio-net
> > NIC should preserve the parallelism (lock free) using multiple
> > receive/transmit queues. The number of queues should equal the
> > number of CPUs.
>
> Yup, multiqueue virtio is on todo list ;-)
>
> thanks,
> -chris
Note we'll need multiqueue tap for that to help.
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
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 13:38:07 +0300 [thread overview]
Message-ID: <20090922103807.GA2555@redhat.com> (raw)
In-Reply-To: <20090921162718.GM26034@sequoia.sous-sol.org>
On Mon, Sep 21, 2009 at 09:27:18AM -0700, Chris Wright wrote:
> * Stephen Hemminger (shemminger@vyatta.com) wrote:
> > On Mon, 21 Sep 2009 16:37:22 +0930
> > Rusty Russell <rusty@rustcorp.com.au> wrote:
> >
> > > > > Actually this framework can apply to traditional network adapters which have
> > > > > just one tx/rx queue pair. And applications using the same user/kernel interface
> > > > > can utilize this framework to send/receive network traffic directly thru a tx/rx
> > > > > queue pair in a network adapter.
> > > > >
> >
> > More importantly, when virtualizations is used with multi-queue
> > NIC's the virtio-net NIC is a single CPU bottleneck. The virtio-net
> > NIC should preserve the parallelism (lock free) using multiple
> > receive/transmit queues. The number of queues should equal the
> > number of CPUs.
>
> Yup, multiqueue virtio is on todo list ;-)
>
> thanks,
> -chris
Note we'll need multiqueue tap for that to help.
--
MST
--
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 10:41 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-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 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 [this message]
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 16:29 ` Stephen Hemminger
2009-09-22 18:34 ` Arnd Bergmann
2009-09-22 18:34 ` Arnd Bergmann
2009-09-22 18:34 ` Arnd Bergmann
2009-09-21 16:27 ` Chris Wright
2009-09-21 16:21 ` 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=20090922103807.GA2555@redhat.com \
--to=mst@redhat.com \
--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=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.