aboutsummaryrefslogtreecommitdiffstats
path: root/rust/helpers/regulator.c
diff options
context:
space:
mode:
authorWill Deacon <[email protected]>2025-07-17 09:01:16 +0000
committerMichael S. Tsirkin <[email protected]>2025-08-01 13:11:09 +0000
commit6693731487a8145a9b039bc983d77edc47693855 (patch)
treec44caf3ac065084048b962ca92db2a90234fb4c0 /rust/helpers/regulator.c
parentvsock/virtio: Rename virtio_vsock_skb_rx_put() (diff)
downloadkernel-6693731487a8145a9b039bc983d77edc47693855.tar.gz
kernel-6693731487a8145a9b039bc983d77edc47693855.zip
vsock/virtio: Allocate nonlinear SKBs for handling large transmit buffers
When transmitting a vsock packet, virtio_transport_send_pkt_info() calls virtio_transport_alloc_linear_skb() to allocate and fill SKBs with the transmit data. Unfortunately, these are always linear allocations and can therefore result in significant pressure on kmalloc() considering that the maximum packet size (VIRTIO_VSOCK_MAX_PKT_BUF_SIZE + VIRTIO_VSOCK_SKB_HEADROOM) is a little over 64KiB, resulting in a 128KiB allocation for each packet. Rework the vsock SKB allocation so that, for sizes with page order greater than PAGE_ALLOC_COSTLY_ORDER, a nonlinear SKB is allocated instead with the packet header in the SKB and the transmit data in the fragments. Note that this affects both the vhost and virtio transports. Reviewed-by: Stefano Garzarella <[email protected]> Signed-off-by: Will Deacon <[email protected]> Message-Id: <[email protected]> Signed-off-by: Michael S. Tsirkin <[email protected]>
Diffstat (limited to 'rust/helpers/regulator.c')
0 files changed, 0 insertions, 0 deletions