mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guo Zhi <qtxuning1999@sjtu.edu.cn>
To: jasowang <jasowang@redhat.com>, Michael Tsirkin <mst@redhat.com>
Cc: eperezma <eperezma@redhat.com>,
	virtualization <virtualization@lists.linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	sgarzare <sgarzare@redhat.com>
Subject: Re: [PATCH v3 0/4] virtio/virtio_test
Date: Wed, 3 Aug 2022 17:00:59 +0800 (CST)	[thread overview]
Message-ID: <2082515061.4772968.1659517259455.JavaMail.zimbra@sjtu.edu.cn> (raw)
In-Reply-To: <4185ee25-52af-8271-c4de-3824490fba6a@sjtu.edu.cn>



----- Original Message -----
> From: "Guo Zhi" <qtxuning1999@sjtu.edu.cn>
> To: "jasowang" <jasowang@redhat.com>, "Michael Tsirkin" <mst@redhat.com>
> Cc: "eperezma" <eperezma@redhat.com>, "virtualization" <virtualization@lists.linux-foundation.org>, "linux-kernel"
> <linux-kernel@vger.kernel.org>, "sgarzare" <sgarzare@redhat.com>
> Sent: Thursday, July 21, 2022 7:55:31 PM
> Subject: Re: [PATCH v3 0/4] virtio/virtio_test

> On 2022/7/9 10:27, Guo Zhi wrote:
>> Original virtio_test only use add one descriptor for each io event, thus code of
>> descriptor chain and indirection have not been tested(one descriptor will not
>> use indirect feature even indirect feature has been specified). In fact it
>> would have not been possible for vhost_test to access to the indirect
>> descriptor table, because it's impossible for virtio_ring.c to allocate it.
>>
>> This series using descriptor chain and enable indirection feature. And through
>> gcov we find the code coverage has been improved(not high for virtio_ring.c
>> because virtio_test only test split virtqueue):
>>
>> +------------+-------------+-------------+
>> |            |virtio_test.c|virtio_ring.c|
>> +------------+-------------+-------------+
>> | original   |   72.32%    |   24.71%    |
>> +------------+-------------+-------------+
>> | current    |    75%      |   28.05%    |
>> +------------+-------------+-------------+
>>
>> Guo Zhi (4):
>>    virtio_test: kick vhost for a batch of descriptors
>>    virtio_test: use random length scatterlists to test descriptor chain
>>    virtio_test: enable indirection feature
>>    virtio_test: pregenerate random numbers
>>
>>   tools/virtio/virtio_test.c | 85 ++++++++++++++++++++++++++++++--------
>>   1 file changed, 68 insertions(+), 17 deletions(-)
>>
> Hi, the new version patch of virtio_test is waiting for review:)
> 
> Thanks.

Friendly ping for the patches:)
Thanks

      reply	other threads:[~2022-08-03  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-09  2:27 Guo Zhi
2022-07-09  2:27 ` [PATCH v3 1/4] virtio_test: kick vhost for a batch of descriptors Guo Zhi
2022-07-09  2:27 ` [PATCH v3 2/4] virtio_test: use random length scatterlists to test descriptor chain Guo Zhi
2022-07-11 15:35   ` Eugenio Perez Martin
2022-07-17 11:33     ` Guo Zhi
2022-07-09  2:27 ` [PATCH v3 3/4] virtio_test: enable indirection feature Guo Zhi
2022-07-09  2:27 ` [PATCH v3 4/4] virtio_test: pregenerate random numbers Guo Zhi
2022-07-21 11:55 ` [PATCH v3 0/4] virtio/virtio_test Guo Zhi
2022-08-03  9:00   ` Guo Zhi [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=2082515061.4772968.1659517259455.JavaMail.zimbra@sjtu.edu.cn \
    --to=qtxuning1999@sjtu.edu.cn \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --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

all inboxes | Powered by JetHome®