From: "Michael S. Tsirkin" <mst@redhat.com>
To: jasowang <jasowang@redhat.com>
Cc: Krishna Kumar2 <krkumar2@in.ibm.com>,
arnd@arndb.de, davem@davemloft.net, levinsasha928@gmail.com,
netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org,
jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH] macvtap: Fix macvtap_get_queue to use rxhash first
Date: Thu, 24 Nov 2011 18:12:49 +0200 [thread overview]
Message-ID: <20111124161249.GB26770@redhat.com> (raw)
In-Reply-To: <4ECE4004.8010107@redhat.com>
On Thu, Nov 24, 2011 at 09:00:52PM +0800, jasowang wrote:
> On 11/24/2011 07:14 PM, Krishna Kumar2 wrote:
> >"Michael S. Tsirkin"<mst@redhat.com> wrote on 11/24/2011 03:29:03 PM:
> >
> >>Subject Re: [PATCH] macvtap: Fix macvtap_get_queue to use rxhash first
> >>
> >>On Thu, Nov 24, 2011 at 01:47:14PM +0530, Krishna Kumar wrote:
> >>>It was reported that the macvtap device selects a
> >>>different vhost (when used with multiqueue feature)
> >>>for incoming packets of a single connection. Use
> >>>packet hash first. Patch tested on MQ virtio_net.
> >>So this is sure to address the problem, why exactly does this happen?
> >>Does your device spread a single flow across multiple RX queues? Would
> >>not that cause trouble in the TCP layer?
> >>It would seem that using the recorded queue should be faster with
> >>less cache misses. Before we give up on that, I'd
> >>like to understand why it's wrong. Do you know?
> >I am using ixgbe. From what I briefly saw, ixgbe_alloc_rx_buffers
> >calls skb_record_rx_queue when a skb is allocated. When a packet
> >is received (ixgbe_alloc_rx_buffers), it sets rxhash. The
> >recorded value is different for most skbs when I ran a single
> >stream TCP stream test (does skbs move between the rx_rings?).
>
> Yes, it moves. It depends on last processor or tx queue who
> transmits the packets of this stream. Because ixgbe select tx queue
> based on the processor id, so if vhost thread transmits skbs on
> different processors, the skb of a single stream may comes from
> different rx ring.
Is that so? In that case, it looks like there's bug on the transmit
side, causing skbs to get scattered between ixgbe tx queues,
and the receive side trouble follows.
> >With this patch, macvtap selects the same device for each
> >incoming packet. I can add some debugs in ixgbe to see what is
> >happening also. I am not sure if Sasha was using a different
> >device.
> >
> >Cc'ing Jeffrey in case he can add something.
> >
> >thanks,
> >
> >- KK
> >
> >--
> >To unsubscribe from this list: send the line "unsubscribe netdev" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-24 16:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 8:17 [PATCH] macvtap: Fix macvtap_get_queue to use rxhash first Krishna Kumar
2011-11-24 9:36 ` jasowang
2011-11-24 9:59 ` Michael S. Tsirkin
2011-11-24 10:13 ` jasowang
2011-11-24 10:34 ` Michael S. Tsirkin
2011-11-24 12:56 ` jasowang
2011-11-24 16:14 ` Michael S. Tsirkin
2011-11-25 3:07 ` Krishna Kumar2
2011-11-25 3:21 ` Jason Wang
2011-11-25 4:09 ` Krishna Kumar2
2011-11-25 6:35 ` David Miller
2011-11-27 17:23 ` Michael S. Tsirkin
2011-11-28 4:40 ` Jason Wang
2011-12-07 16:10 ` Michael S. Tsirkin
2011-12-07 18:52 ` David Miller
2011-12-20 11:15 ` Michael S. Tsirkin
2011-12-20 18:46 ` David Miller
2011-12-08 9:46 ` Jason Wang
2011-11-27 17:14 ` Michael S. Tsirkin
2011-11-28 4:25 ` Jason Wang
2011-11-28 17:42 ` Stephen Hemminger
2011-11-25 3:09 ` Jason Wang
2011-11-24 11:14 ` Krishna Kumar2
2011-11-24 13:00 ` jasowang
2011-11-24 16:12 ` Michael S. Tsirkin [this message]
2011-11-25 2:58 ` Krishna Kumar2
2011-11-25 3:18 ` Jason Wang
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=20111124161249.GB26770@redhat.com \
--to=mst@redhat.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=krkumar2@in.ibm.com \
--cc=levinsasha928@gmail.com \
--cc=netdev@vger.kernel.org \
--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).