From: David Miller <davem@davemloft.net>
To: werekraken@gmail.com
Cc: jasowang@redhat.com, brouer@redhat.com, mst@redhat.com,
edumazet@google.com, sd@queasysnail.net, netdev@vger.kernel.org,
matthew.cover@stackpath.com
Subject: Re: [PATCH] [PATCH net-next] tun: fix multiqueue rx
Date: Sat, 17 Nov 2018 20:39:14 -0800 (PST) [thread overview]
Message-ID: <20181117.203914.759473723265367356.davem@davemloft.net> (raw)
In-Reply-To: <20181116041016.39852-1-matthew.cover@stackpath.com>
From: Matthew Cover <werekraken@gmail.com>
Date: Thu, 15 Nov 2018 21:10:16 -0700
> When writing packets to a descriptor associated with a combined queue, the
> packets should end up on that queue.
>
> Before this change all packets written to any descriptor associated with a
> tap interface end up on rx-0, even when the descriptor is associated with a
> different queue.
>
> The rx traffic can be generated by either of the following.
> 1. a simple tap program which spins up multiple queues and writes packets
> to each of the file descriptors
> 2. tx from a qemu vm with a tap multiqueue netdev
>
> The queue for rx traffic can be observed by either of the following (done
> on the hypervisor in the qemu case).
> 1. a simple netmap program which opens and reads from per-queue
> descriptors
> 2. configuring RPS and doing per-cpu captures with rxtxcpu
>
> Alternatively, if you printk() the return value of skb_get_rx_queue() just
> before each instance of netif_receive_skb() in tun.c, you will get 65535
> for every skb.
>
> Calling skb_record_rx_queue() to set the rx queue to the queue_index fixes
> the association between descriptor and rx queue.
>
> Signed-off-by: Matthew Cover <matthew.cover@stackpath.com>
As noted by Jason, tun_xdp_one() needs this fix too.
Can you please add that to your patch and resubmit?
Thanks.
prev parent reply other threads:[~2018-11-18 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 4:10 [PATCH] [PATCH net-next] tun: fix multiqueue rx Matthew Cover
2018-11-16 6:29 ` Jason Wang
2018-11-16 7:00 ` Matthew Cover
2018-11-16 7:11 ` Jason Wang
2018-11-16 20:10 ` Michael S. Tsirkin
2018-11-16 20:45 ` Matt Cover
2018-11-18 5:11 ` David Miller
2018-11-18 7:46 ` [PATCH net] tuntap: " Matthew Cover
2018-11-19 3:06 ` David Miller
2018-11-18 4:39 ` David Miller [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=20181117.203914.759473723265367356.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brouer@redhat.com \
--cc=edumazet@google.com \
--cc=jasowang@redhat.com \
--cc=matthew.cover@stackpath.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=werekraken@gmail.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 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).