From: Luca Vizzarro <Luca.Vizzarro@arm.com>
To: Koushik Bhargav Nimoji <knimoji@iol.unh.edu>
Cc: patrickrobb1997@gmail.com, dev@dpdk.org, dladd@iol.unh.edu,
abailey@iol.unh.edu, lylavoie@iol.unh.edu
Subject: Re: [PATCH v3 2/2] dts: add pvp multi paths virtio performance testsuite
Date: Tue, 3 Nov 2026 15:47:41 +0000 [thread overview]
Message-ID: <5412e441-d415-4c66-a481-35fbc4b73c03@arm.com> (raw)
In-Reply-To: <CAKYPG+z88eQG1zPcSZpQ-jKhsfKuBATcnqoS9wUq0=cKe+Fn4Q@mail.gmail.com>
On 03/11/2026 15:37, Koushik Bhargav Nimoji wrote:
> Hi Luca, this is the virtio single core performance test suite, very
> similar to the vhost single core performance test suite. The difference
> between the two is that in this test suite the virtio virtual device is
> provided one core while the vhost is provided two cores, and vice versa
> in the vhost single core performance test suite. I will apply the
> changes mentioned in the 1/2 in this patch as well, and send new
> versions in shortly.
Oh, alright! Thank you for clarifying! The difference was so subtle I
struggled to notice! In that case the comments I made for the vhost
patches apply here too as, as you picked up already.
Luca
next prev parent reply other threads:[~2026-11-03 15:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 18:37 [RFC PATCH] dts: add pvp multi paths virtio performance testsuite Koushik Bhargav Nimoji
2026-09-03 20:11 ` [PATCH v1] " Koushik Bhargav Nimoji
2026-10-08 19:11 ` [PATCH v2 1/2] dts: add pvp multi paths vhost " Koushik Bhargav Nimoji
2026-10-08 19:11 ` [PATCH v2 2/2] dts: add pvp multi paths virtio " Koushik Bhargav Nimoji
2026-10-19 18:58 ` Andrew Bailey
2026-10-19 18:36 ` [PATCH v2 1/2] dts: add pvp multi paths vhost " Andrew Bailey
2026-10-20 17:30 ` [PATCH v3 " Koushik Bhargav Nimoji
2026-10-20 17:30 ` [PATCH v3 2/2] dts: add pvp multi paths virtio " Koushik Bhargav Nimoji
2026-10-29 17:01 ` Luca Vizzarro
2026-11-03 15:37 ` Koushik Bhargav Nimoji
2026-11-03 15:47 ` Luca Vizzarro [this message]
2026-10-29 16:53 ` [PATCH v3 1/2] dts: add pvp multi paths vhost " Luca Vizzarro
2026-11-03 20:28 ` Koushik Bhargav Nimoji
2026-11-03 22:02 ` [PATCH v4 " Koushik Bhargav Nimoji
2026-11-03 22:02 ` [PATCH v4 2/2] dts: add pvp multi paths virtio " Koushik Bhargav Nimoji
2026-11-10 12:51 ` Luca Vizzarro
2026-11-10 12:50 ` [PATCH v4 1/2] dts: add pvp multi paths vhost " Luca Vizzarro
2026-11-10 15:40 ` Koushik Bhargav Nimoji
2026-11-10 20:10 ` [PATCH v5 " Koushik Bhargav Nimoji
2026-11-10 20:10 ` [PATCH v5 2/2] dts: add pvp multi paths virtio " Koushik Bhargav Nimoji
2026-11-11 16:30 ` [PATCH v5 1/2] dts: add pvp multi paths vhost " Luca Vizzarro
2026-11-12 15:48 ` Koushik Bhargav Nimoji
2026-11-12 21:00 ` [PATCH v6 1/3] dts: create default performance test configuration Koushik Bhargav Nimoji
2026-11-12 21:00 ` [PATCH v6 2/3] dts: add pvp multi paths vhost performance testsuite Koushik Bhargav Nimoji
2026-11-12 21:00 ` [PATCH v6 3/3] dts: add pvp multi paths virtio " Koushik Bhargav Nimoji
2026-11-19 18:41 ` [PATCH v6 1/3] dts: create default performance test configuration Luca Vizzarro
2026-11-20 12:02 ` Thomas Monjalon
2026-10-20 18:20 ` [RFC PATCH] dts: add pvp multi paths virtio performance testsuite Koushik Bhargav Nimoji
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=5412e441-d415-4c66-a481-35fbc4b73c03@arm.com \
--to=luca.vizzarro@arm.com \
--cc=abailey@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=dladd@iol.unh.edu \
--cc=knimoji@iol.unh.edu \
--cc=lylavoie@iol.unh.edu \
--cc=patrickrobb1997@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox