sunvnet: Use multiple Tx queues.
Subsystems (2)
v2 cover sunvnet: Use multiple Tx queues.
v2: moved tcp fix out of this series per David Miller feedback
The primary objective of this patch-set is to address the suggestion from
http://marc.info/?l=linux-netdev&m=140790778931563&w=2
With the changes in Patch 2, every vnet_port will get packets from a single tx-queue, and flow-control/head-of-line-blocking is confined to the vnet_ports that share that tx queue (as opposed to flow-controlling *all* peers).
Patch 1 is an optimization that resets the DATA_READY bit when we re-enable Rx interrupts. This optimization lets us exit quickly from vnet_event_napi() when new data has not triggered an interrupt.
Sowmini Varadhan (3):
Correction to RFC number in comment
Reset LDC_EVENT_DATA_READY when napi completes.
Use one Tx queue per vnet_port
drivers/net/ethernet/sun/sunvnet.c | 95 +++++++++++++++++++++++++------------- drivers/net/ethernet/sun/sunvnet.h | 2 + net/ipv4/tcp_input.c | 2 +- 3 files changed, 67 insertions(+), 32 deletions(-)
Signature · 1 line
1.8.4.2
David Miller
maintainerFrom: Sowmini Varadhan <[email protected]>
Date: Thu, 30 Oct 2014 12:45:47 -0400
Quoted 10 lines
v2: moved tcp fix out of this series per David Miller feedback
The primary objective of this patch-set is to address the suggestion from
http://marc.info/?l=linux-netdev&m=140790778931563&w=2
With the changes in Patch 2, everyvnet_portwill get packets from a single tx-queue, and flow-control/head-of-line-blocking is confined to thevnet_portsthat share that tx queue (as opposed to flow-controlling *all* peers).
Quoted 3 lines
Patch 1 is an optimization that resets the
DATA_READYbit when we re-enable Rx interrupts. This optimization lets us exit quickly fromvnet_event_napi()when new data has not triggered an interrupt.
This looks great, series applied to net-next, thanks.