diff options
author | Matthew Cover <werekraken@gmail.com> | 2018-11-18 08:46:00 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-11-19 04:05:43 +0100 |
commit | 8ebebcba559a1bfbaec7bbda64feb9870b9c58da (patch) | |
tree | 8cccb1975f0c8563935257b8abcccc2b28d66394 /net | |
parent | ipv6: Fix PMTU updates for UDP/raw sockets in presence of VRF (diff) | |
download | linux-8ebebcba559a1bfbaec7bbda64feb9870b9c58da.tar.xz linux-8ebebcba559a1bfbaec7bbda64feb9870b9c58da.zip |
tuntap: fix multiqueue rx
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>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions