From: sashiko-bot@kernel.org
To: "sung byeongchan" <tjdqudcks0424@naver.com>
Cc: "Eugenio Perez" <eperezma@redhat.com>,
virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v3] virtio_ring: use shadow flags when detaching split descriptors
Date: Thu, 08 Oct 2026 05:12:03 +0000 [thread overview]
Message-ID: <sashiko-outbox-163622@kernel.org> (raw)
In-Reply-To: <20261008050423.32221-1-tjdqudcks0424@naver.com>
> From: sungbyeongchan <tjdqudcks0424@naver.com>
>
> Split virtqueues save descriptor flags and next indexes in desc_extra
> before publishing descriptors to the device. The detach path uses the
> shadow next index, but decides whether to continue by rereading the NEXT
> flag from the shared descriptor.
>
> Use the shadow flags for the continuation decision as well. This keeps
> all detach metadata in the same driver-owned snapshot and avoids an
> unnecessary shared-ring read.
>
> Fixes: 72b5e8958738 ("virtio-ring: store DMA metadata in desc_extra for split virtqueue")
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
> Assisted-by: LLM
> Signed-off-by: sungbyeongchan <tjdqudcks0424@naver.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261008050423.32221-1-tjdqudcks0424@naver.com?part=1
next prev parent reply other threads:[~2026-10-08 5:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 10:21 [PATCH v2] virtio_ring: use shadow flags when detaching split descriptors sungbyeongchan
2026-10-06 10:29 ` sashiko-bot
2026-10-08 1:21 ` Xuan Zhuo
2026-10-08 6:19 ` Michael S. Tsirkin
2026-10-08 5:04 ` [PATCH v3] " sung byeongchan
2026-10-08 5:12 ` sashiko-bot [this message]
2026-10-08 7:02 ` Michael S. Tsirkin
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-163622@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=mst@redhat.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=tjdqudcks0424@naver.com \
--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