From: "Michael S. Tsirkin" <mst@redhat.com>
To: sung byeongchan <tjdqudcks0424@naver.com>
Cc: "Jason Wang" <jasowangio@gmail.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] virtio_ring: use shadow flags when detaching split descriptors
Date: Thu, 8 Oct 2026 03:02:11 -0400 [thread overview]
Message-ID: <20261008030121-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20261008050423.32221-1-tjdqudcks0424@naver.com>
On Thu, Oct 08, 2026 at 02:04:23PM +0900, sung byeongchan wrote:
> 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>
> ---
Thanks, will apply! Can you pls confirm sungbyeongchan without space is your
preferred form to be called, and not a mistake?
> Changes in v3:
> - Restore a concise commit message explaining the mixed shared/shadow
> metadata problem. The v2 response had removed the whole description.
> - Keep Michael's Acked-by.
> - No code changes.
>
> Changes in v2:
> - Drop the two paragraphs Michael identified as unnecessary.
> - Add Michael's Acked-by.
>
> drivers/virtio/virtio_ring.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
> index db678f5a80e03..b4cb433df1dec 100644
> --- a/drivers/virtio/virtio_ring.c
> +++ b/drivers/virtio/virtio_ring.c
> @@ -905,7 +905,6 @@ static unsigned detach_buf_split_in_order(struct vring_virtqueue *vq,
> {
> struct vring_desc_extra *extra;
> unsigned int i;
> - __virtio16 nextflag = cpu_to_virtio16(vq->vq.vdev, VRING_DESC_F_NEXT);
>
> /* Clear data ptr. */
> vq->split.desc_state[head].data = NULL;
> @@ -915,7 +914,7 @@ static unsigned detach_buf_split_in_order(struct vring_virtqueue *vq,
> /* Put back on free list: unmap first-level descriptors and find end */
> i = head;
>
> - while (vq->split.vring.desc[i].flags & nextflag) {
> + while (extra[i].flags & VRING_DESC_F_NEXT) {
> i = vring_unmap_one_split(vq, &extra[i]);
> vq->vq.num_free++;
> }
> base-commit: 0c2669a9f4a1d607e7591ae50ccf3c432a0aff08
> --
> 2.43.0
prev parent reply other threads:[~2026-10-08 7:02 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
2026-10-08 7:02 ` Michael S. Tsirkin [this message]
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=20261008030121-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tjdqudcks0424@naver.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.