diff options
| author |   Paolo Abeni <pabeni@redhat.com> | 2025-07-03 11:40:04 +0200 |
|---|---|---|
| committer | Paolo Abeni <pabeni@redhat.com> | 2025-07-03 11:40:04 +0200 |
| commit | b0727b0ccd907aa669ba48027f29019f1c48d42c (patch) | |
| tree | 27c56a662c6e7a5530d251c88cfec275738b98d6 /rust/pin-init/internal/src | |
| parent | virtio-net: xsk: rx: fix the frame's length check (diff) | |
| parent | virtio_net: Enforce minimum TX ring size for reliability (diff) | |
| download | wireguard-linux-b0727b0ccd907aa669ba48027f29019f1c48d42c.tar.xz wireguard-linux-b0727b0ccd907aa669ba48027f29019f1c48d42c.zip | |
Merge branch 'virtio-fixes-for-tx-ring-sizing-and-resize-error-reporting'
Laurent Vivier says:
====================
virtio: Fixes for TX ring sizing and resize error reporting
This patch series contains two fixes and a cleanup for the virtio subsystem.
The first patch fixes an error reporting bug in virtio_ring's
virtqueue_resize() function. Previously, errors from internal resize
helpers could be masked if the subsequent re-enabling of the virtqueue
succeeded. This patch restores the correct error propagation, ensuring that
callers of virtqueue_resize() are properly informed of underlying resize
failures.
The second patch does a cleanup of the use of '2+MAX_SKB_FRAGS'
The third patch addresses a reliability issue in virtio_net where the TX
ring size could be configured too small, potentially leading to
persistently stopped queues and degraded performance. It enforces a
minimum TX ring size to ensure there's always enough space for at least one
maximally-fragmented packet plus an additional slot.
====================
Link: https://patch.msgid.link/20250521092236.661410-1-lvivier@redhat.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'rust/pin-init/internal/src')
0 files changed, 0 insertions, 0 deletions