Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Daehyeon Ko" <4ncienth@gmail.com>
Cc: "Eugenio Perez" <eperezma@redhat.com>,
	kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	virtualization@lists.linux.dev
Subject: Re: [PATCH net] vhost/vsock: trim nonlinear SKBs to declared payload length
Date: Wed, 30 Sep 2026 04:49:51 +0000	[thread overview]
Message-ID: <20260930044951.EED0F1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930044147.3818241-1-4ncienth@gmail.com>

> vhost_vsock_alloc_skb() sizes its skb from the total guest descriptor
> length, while virtio_vsock_hdr.len independently declares the payload
> length.  Since commit ab9aa2f3afc2 ("vhost/vsock: Allocate nonlinear SKBs
> for handling large receive buffers"), large descriptors use skb fragments.
> 
> virtio_vsock_skb_put() currently changes only skb->len for a nonlinear
> skb, leaving skb->data_len and all fragments attached.  The zero-payload
> fast path skips the helper entirely.  A guest can therefore retain the
> full descriptor allocation while receive credit accounts no payload.
> 
> On Linux v7.2, 455 zero-payload skbs retained 30,255,680 bytes on a
> 256 KiB receive buffer while rx_bytes and buf_used remained zero.  A
> full-payload control retained 265,984 bytes in four skbs.  The existing
> SKB_TRUESIZE(0) queue budget caps skb count but does not account for these
> descriptor-sized fragments.
> [ ... ]
> 
> Fixes: ab9aa2f3afc2 ("vhost/vsock: Allocate nonlinear SKBs for handling large receive buffers")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Daehyeon Ko <4ncienth@gmail.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260930044147.3818241-1-4ncienth@gmail.com?part=1


  reply	other threads:[~2026-09-30  4:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  4:41 [PATCH net] vhost/vsock: trim nonlinear SKBs to declared payload length Daehyeon Ko
2026-09-30  4:49 ` sashiko-bot [this message]
2026-10-01 10:17 ` Stefano Garzarella
2026-10-04  4:57 ` netdev-bot+sashiko
2026-10-04  7:33   ` Daehyeon Ko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260930044951.EED0F1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=4ncienth@gmail.com \
    --cc=eperezma@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=virtualization@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox