From: Jason Wang <jasowang@redhat.com>
To: Guo Zhi <qtxuning1999@sjtu.edu.cn>,
eperezma@redhat.com, sgarzare@redhat.com, mst@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [RFC v2 2/7] vhost_test: batch used buffer
Date: Thu, 25 Aug 2022 15:03:43 +0800 [thread overview]
Message-ID: <06761c62-93b4-8eaa-370f-f26b7c5306ca@redhat.com> (raw)
In-Reply-To: <20220817135718.2553-3-qtxuning1999@sjtu.edu.cn>
在 2022/8/17 21:57, Guo Zhi 写道:
> Only add to used ring when a batch of buffer have all been used. And if
> in order feature negotiated, only add the last used descriptor for a
> batch of buffer.
>
> Signed-off-by: Guo Zhi <qtxuning1999@sjtu.edu.cn>
> ---
> drivers/vhost/test.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/vhost/test.c b/drivers/vhost/test.c
> index bc8e7fb1e635..57cdb3a3edf6 100644
> --- a/drivers/vhost/test.c
> +++ b/drivers/vhost/test.c
> @@ -43,6 +43,9 @@ struct vhost_test {
> static void handle_vq(struct vhost_test *n)
> {
> struct vhost_virtqueue *vq = &n->vqs[VHOST_TEST_VQ];
> + struct vring_used_elem *heads = kmalloc(sizeof(*heads)
> + * vq->num, GFP_KERNEL);
Though it's a test device, it would be better to try avoid memory
allocation in the datapath.
And where is is freed?
Thanks
> + int batch_idx = 0;
> unsigned out, in;
> int head;
> size_t len, total_len = 0;
> @@ -84,11 +87,14 @@ static void handle_vq(struct vhost_test *n)
> vq_err(vq, "Unexpected 0 len for TX\n");
> break;
> }
> - vhost_add_used_and_signal(&n->dev, vq, head, 0);
> + heads[batch_idx].id = cpu_to_vhost32(vq, head);
> + heads[batch_idx++].len = cpu_to_vhost32(vq, len);
> total_len += len;
> if (unlikely(vhost_exceeds_weight(vq, 0, total_len)))
> break;
> }
> + if (batch_idx)
> + vhost_add_used_and_signal_n(&n->dev, vq, heads, batch_idx);
>
> mutex_unlock(&vq->mutex);
> }
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-08-25 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220817135718.2553-1-qtxuning1999@sjtu.edu.cn>
[not found] ` <20220817135718.2553-6-qtxuning1999@sjtu.edu.cn>
2022-08-18 3:05 ` [RFC v2 5/7] virtio: unmask F_NEXT flag in desc_extra Xuan Zhuo
2022-08-25 7:11 ` Jason Wang
[not found] ` <20220817135718.2553-2-qtxuning1999@sjtu.edu.cn>
2022-08-25 7:01 ` [RFC v2 1/7] vhost: expose used buffers Jason Wang
[not found] ` <20220817135718.2553-3-qtxuning1999@sjtu.edu.cn>
2022-08-25 7:03 ` Jason Wang [this message]
[not found] ` <20220817135718.2553-4-qtxuning1999@sjtu.edu.cn>
2022-08-25 7:08 ` [RFC v2 3/7] vsock: batch buffers in tx Jason Wang
[not found] ` <20220817135718.2553-7-qtxuning1999@sjtu.edu.cn>
2022-08-18 3:11 ` [RFC v2 6/7] virtio: in order support for virtio_ring Xuan Zhuo
2022-08-25 7:44 ` Jason Wang
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=06761c62-93b4-8eaa-370f-f26b7c5306ca@redhat.com \
--to=jasowang@redhat.com \
--cc=eperezma@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=qtxuning1999@sjtu.edu.cn \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).