From: sashiko-bot@kernel.org
To: "Jia Jia" <physicalmtea@gmail.com>
Cc: virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH net-next v5 1/5] vsock/virtio: split socket lookup from locked RX processing
Date: Fri, 23 Oct 2026 08:14:29 +0000 [thread overview]
Message-ID: <sashiko-outbox-182489@kernel.org> (raw)
In-Reply-To: <20261023075140.9613-2-physicalmtea@gmail.com>
> Split virtio_transport_recv_pkt() so socket lookup is separate from
> processing that occurs while holding the socket lock. This prepares the
> receive path to retain a looked-up socket across multiple packets in a
> later change.
>
> Keep virtio_transport_recv_pkt() on its existing per-packet locking path.
> Pass the caller-provided network namespace to the locked helper so reset
> handling retains its existing semantics. Preserve source validation and
> failure handling.
>
> Signed-off-by: Jia Jia <physicalmtea@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261023075140.9613-1-physicalmtea@gmail.com?part=1
next prev parent reply other threads:[~2026-10-23 8:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 7:51 [PATCH net-next v5 0/5] vsock/virtio: reduce RX per-packet socket overhead Jia Jia
2026-10-23 7:51 ` [PATCH net-next v5 1/5] vsock/virtio: split socket lookup from locked RX processing Jia Jia
2026-10-23 8:14 ` sashiko-bot [this message]
2026-10-23 7:51 ` [PATCH net-next v5 2/5] vsock/virtio: factor RX skb metadata budget check Jia Jia
2026-10-23 8:14 ` sashiko-bot
2026-10-23 7:51 ` [PATCH net-next v5 3/5] vsock/virtio: amortize RX socket locking for stream packets Jia Jia
2026-10-23 8:14 ` sashiko-bot
2026-10-23 7:51 ` [PATCH net-next v5 4/5] vsock/virtio: coalesce native RX write-space notifications Jia Jia
2026-10-23 8:14 ` sashiko-bot
2026-10-23 7:51 ` [PATCH net-next v5 5/5] vsock/virtio: defer native RX readiness notifications until batch unlock Jia Jia
2026-10-23 8:14 ` sashiko-bot
2026-10-27 12:20 ` [PATCH net-next v5 0/5] vsock/virtio: reduce RX per-packet socket overhead Paolo Abeni
-- strict thread matches above, loose matches on Subject: below --
2026-11-03 4:11 Jia Jia
2026-11-03 4:11 ` [PATCH net-next v5 1/5] vsock/virtio: split socket lookup from locked RX processing Jia Jia
2026-11-05 9:04 ` Stefano Garzarella
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=sashiko-outbox-182489@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=mst@redhat.com \
--cc=physicalmtea@gmail.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