| Message ID | 20231005140831.89117-1-roger.pau@citrix.com (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | 66cf7435a26917c0c4d6245ad9137e7606e84fdf |
| Delegated to: | Netdev Maintainers |
| Headers | show |
| Series | xen-netback: use default TX queue size for vifs | expand |
On Thu, Oct 5, 2023 at 3:08 PM Roger Pau Monne <roger.pau@citrix.com> wrote: > > Do not set netback interfaces (vifs) default TX queue size to the ring size. > The TX queue size is not related to the ring size, and using the ring size (32) > as the queue size can lead to packet drops. Note the TX side of the vif > interface in the netback domain is the one receiving packets to be injected > to the guest. > > Do not explicitly set the TX queue length to any value when creating the > interface, and instead use the system default. Note that the queue length can > also be adjusted at runtime. > > Fixes: f942dc2552b8 ('xen network backend driver') > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> > --- Reviewed-by: Ross Lagerwall <ross.lagerwall@citrix.com>
On Thu, Oct 05, 2023 at 04:08:31PM +0200, Roger Pau Monne wrote: > Do not set netback interfaces (vifs) default TX queue size to the ring size. > The TX queue size is not related to the ring size, and using the ring size (32) > as the queue size can lead to packet drops. Note the TX side of the vif > interface in the netback domain is the one receiving packets to be injected > to the guest. > > Do not explicitly set the TX queue length to any value when creating the > interface, and instead use the system default. Note that the queue length can > also be adjusted at runtime. > > Fixes: f942dc2552b8 ('xen network backend driver') > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Acked-by: Wei Liu <wei.liu@kernel.org>
Hello: This patch was applied to netdev/net.git (main) by David S. Miller <davem@davemloft.net>: On Thu, 5 Oct 2023 16:08:31 +0200 you wrote: > Do not set netback interfaces (vifs) default TX queue size to the ring size. > The TX queue size is not related to the ring size, and using the ring size (32) > as the queue size can lead to packet drops. Note the TX side of the vif > interface in the netback domain is the one receiving packets to be injected > to the guest. > > Do not explicitly set the TX queue length to any value when creating the > interface, and instead use the system default. Note that the queue length can > also be adjusted at runtime. > > [...] Here is the summary with links: - xen-netback: use default TX queue size for vifs https://git.kernel.org/netdev/net/c/66cf7435a269 You are awesome, thank you!
diff --git a/drivers/net/xen-netback/interface.c b/drivers/net/xen-netback/interface.c index f3f2c07423a6..fc3bb63b9ac3 100644 --- a/drivers/net/xen-netback/interface.c +++ b/drivers/net/xen-netback/interface.c @@ -41,8 +41,6 @@ #include <asm/xen/hypercall.h> #include <xen/balloon.h> -#define XENVIF_QUEUE_LENGTH 32 - /* Number of bytes allowed on the internal guest Rx queue. */ #define XENVIF_RX_QUEUE_BYTES (XEN_NETIF_RX_RING_SIZE/2 * PAGE_SIZE) @@ -530,8 +528,6 @@ struct xenvif *xenvif_alloc(struct device *parent, domid_t domid, dev->features = dev->hw_features | NETIF_F_RXCSUM; dev->ethtool_ops = &xenvif_ethtool_ops; - dev->tx_queue_len = XENVIF_QUEUE_LENGTH; - dev->min_mtu = ETH_MIN_MTU; dev->max_mtu = ETH_MAX_MTU - VLAN_ETH_HLEN;
Do not set netback interfaces (vifs) default TX queue size to the ring size. The TX queue size is not related to the ring size, and using the ring size (32) as the queue size can lead to packet drops. Note the TX side of the vif interface in the netback domain is the one receiving packets to be injected to the guest. Do not explicitly set the TX queue length to any value when creating the interface, and instead use the system default. Note that the queue length can also be adjusted at runtime. Fixes: f942dc2552b8 ('xen network backend driver') Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> --- drivers/net/xen-netback/interface.c | 4 ---- 1 file changed, 4 deletions(-)