netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Jason Wang <jasowang@redhat.com>
Cc: krkumar2@in.ibm.com, eric.dumazet@gmail.com, mst@redhat.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org, davem@davemloft.net,
	kvm@vger.kernel.org, rusty@rustcorp.com.au,
	qemu-devel@nongnu.org, mirq-linux@rere.qmqm.pl, joe@perches.com,
	shemminger@vyatta.com
Subject: Re: [net-next RFC V2 PATCH 0/5] Multiqueue support in tun/tap
Date: Mon, 19 Sep 2011 15:45:51 +0100	[thread overview]
Message-ID: <1316443551.2764.9.camel@bwh-desktop> (raw)
In-Reply-To: <20110917055639.32666.89940.stgit@dhcp-91-7.nay.redhat.com.englab.nay.redhat.com>

On Sat, 2011-09-17 at 14:02 +0800, Jason Wang wrote:
[...]
> 2 Current implementation may also get regression for single session
> packet transmission.
> 
> The reason is packets from each flow were not handled by the same
> queue/vhost thread.
> 
> Various method could be done to handle this:
> 
> 2.1 hack the guest driver, and store the queue index into the rxhash and
> use it when choosing tx in guest. This need some hack to store the
> rxhash into sk and pass it in to skb again in
> skb_orphan_try(). sk_rxhash is only used by RPS now, so some more
> clean method is needed.
[...]

I have previously suggested doing this as a general rule.  However, I
now think we can do much better with accelerated RFS and automatic XPS
(but the latter is not yet implemented).  For virtio_net, accelerated
RFS would effectively push the guest's RFS socket map out to the host.

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

      parent reply	other threads:[~2011-09-19 14:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-17  6:02 [net-next RFC V2 PATCH 0/5] Multiqueue support in tun/tap Jason Wang
2011-09-17  6:02 ` [net-next RFC V2 PATCH 1/5] tuntap: move socket to tun_file Jason Wang
2011-09-17  6:02 ` [net-next RFC V2 PATCH 2/5] tuntap: categorize ioctl Jason Wang
2011-09-17  6:02 ` [net-next RFC V2 PATCH 3/5] tuntap: introduce multiqueue flags Jason Wang
2011-09-17  6:02 ` [net-next RFC V2 PATCH 4/5] tuntap: multiqueue support Jason Wang
2011-09-17  6:03 ` [net-next RFC V2 PATCH 5/5] tuntap: add ioctls to attach or detach a file form tap device Jason Wang
2011-09-17 19:17 ` [net-next RFC V2 PATCH 0/5] Multiqueue support in tun/tap Michael S. Tsirkin
2011-09-19  9:44   ` Jason Wang
2011-09-19 14:45 ` Ben Hutchings [this message]

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=1316443551.2764.9.camel@bwh-desktop \
    --to=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=joe@perches.com \
    --cc=krkumar2@in.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rusty@rustcorp.com.au \
    --cc=shemminger@vyatta.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).