From: Hawkins Jiawei <yin31149@gmail.com>
To: eperezma@redhat.com, jasowang@redhat.com
Cc: yin31149@gmail.com, 18801353760@163.com, qemu-devel@nongnu.org
Subject: [PATCH 0/2] Send all the SVQ control commands in parallel
Date: Wed, 19 Apr 2023 19:49:51 +0800 [thread overview]
Message-ID: <cover.1681732982.git.yin31149@gmail.com> (raw)
This patchset allows QEMU to poll and check the device used buffer
after sending all SVQ control commands, instead of polling and checking
immediately after sending each SVQ control command, so that QEMU can
send all the SVQ control commands in parallel, which have better
performance improvement.
I use vdpa_sim_net to simulate vdpa device, refactor
vhost_vdpa_net_load() to call vhost_vdpa_net_load_mac() 30 times,
refactor `net_vhost_vdpa_cvq_info.load` to call vhost_vdpa_net_load()
1000 times, to build a test environment for sending
multiple SVQ control commands. Time in monotonic to
finish `net_vhost_vdpa_cvq_info.load`:
QEMU monotonic time
--------------------------------------------------
not patched 89202
--------------------------------------------------
patched 80455
This patchset resolves the GitLab issue at
https://gitlab.com/qemu-project/qemu/-/issues/1578.
Hawkins Jiawei (2):
vdpa: rename vhost_vdpa_net_cvq_add()
vdpa: send CVQ state load commands in parallel
net/vhost-vdpa.c | 150 +++++++++++++++++++++++++++++++++++------------
1 file changed, 112 insertions(+), 38 deletions(-)
--
2.25.1
next reply other threads:[~2023-04-19 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 11:49 Hawkins Jiawei [this message]
2023-04-19 11:49 ` [PATCH 1/2] vdpa: rename vhost_vdpa_net_cvq_add() Hawkins Jiawei
2023-04-19 11:49 ` [PATCH 2/2] vdpa: send CVQ state load commands in parallel Hawkins Jiawei
2023-04-19 17:42 ` Eugenio Perez Martin
2023-04-20 11:38 ` Hawkins Jiawei
2023-04-20 15:22 ` Hawkins Jiawei
2023-04-19 17:16 ` [PATCH 0/2] Send all the SVQ control " Eugenio Perez Martin
2023-04-20 8:32 ` Hawkins Jiawei
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=cover.1681732982.git.yin31149@gmail.com \
--to=yin31149@gmail.com \
--cc=18801353760@163.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.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).