mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"virtualization@lists.linux-foundation.org" 
	<virtualization@lists.linux-foundation.org>,
	Bobby Eshleman <bobby.eshleman@gmail.com>,
	kernel <kernel@sberdevices.ru>,
	Krasnov Arseniy <oxffffaa@gmail.com>
Subject: [RFC PATCH v1 0/3] test/vsock: update two tests and add new tool
Date: Tue, 15 Nov 2022 20:48:05 +0000	[thread overview]
Message-ID: <ba294dff-812a-bfc2-a43c-286f99aee0b8@sberdevices.ru> (raw)

Since there is work on several significant updates for vsock(virtio/
vsock especially): skbuff, DGRAM, zerocopy rx/tx, so I think that this
patchset will be useful.

This patchset updates vsock tests and tools a little bit. First of all
it updates test suite: two new tests are added. One test is reworked
message bound test. Now it is more complex. Instead of sending 1 byte
messages with one MSG_EOR bit, it sends messages of random length(one
half of messages are smaller than page size, second half are bigger)
with random number of MSG_EOR bits set. Receiver also don't know total
number of messages. Message bounds control is maintained by hash sum
of messages length calculation. Second test is for SOCK_SEQPACKET - it
tries to send message with length more than allowed. I think both tests
will be useful for DGRAM support also.

Third thing that this patchset adds is small utility to test vsock
performance for both rx and tx. I think this util could be useful as
'iperf', because:
1) It is small comparing to 'iperf()', so it very easy to add new
   mode or feature to it(especially vsock specific).
2) It is located in kernel source tree, so it could be updated by the
   same patchset which changes related kernel functionality in vsock.

I used this util very often to check performance of my rx zerocopy
support(this tool has rx zerocopy support, but not in this patchset).

Patchset was rebased and tested on skbuff patch from Bobby Eshleman:
https://lore.kernel.org/lkml/20221110171723.24263-1-bobby.eshleman@bytedance.com/

All 3 patches are from my previous big patchset for virtio/vsock rx
zerocopy - they are not related to zerocopy, so Stefano suggested to
exclude them from patchset.

Arseniy Krasnov(3):
 test/vsock: rework message bound test
 test/vsock: add big message test
 test/vsock: vsock_perf utility

 tools/testing/vsock/Makefile     |   1 +
 tools/testing/vsock/vsock_perf.c | 386 +++++++++++++++++++++++++++++++++++++++
 tools/testing/vsock/vsock_test.c |  62 +++++++
 3 files changed, 449 insertions(+)

-- 
2.25.1

             reply	other threads:[~2022-11-15 20:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 20:48 Arseniy Krasnov [this message]
2022-11-15 20:50 ` [RFC PATCH v1 1/3] test/vsock: rework message bound test Arseniy Krasnov
2022-11-21 14:46   ` Stefano Garzarella
2022-11-21 16:49     ` Arseniy Krasnov
2022-11-23 15:24       ` Stefano Garzarella
2022-11-15 20:52 ` [RFC PATCH v1 2/3] test/vsock: add big message test Arseniy Krasnov
2022-11-21 14:52   ` Stefano Garzarella
2022-11-21 16:50     ` Arseniy Krasnov
2022-11-21 21:40       ` Arseniy Krasnov
2022-11-23 15:21         ` Stefano Garzarella
     [not found]           ` <CAKB00G0vcy3EkoouzTsZ8OYZ7hJRFxQ4ThUm4f0ALVs6maFd2g@mail.gmail.com>
2022-11-23 16:28             ` Arseniy Krasnov
2022-11-15 20:54 ` [RFC PATCH v1 3/3] test/vsock: vsock_perf utility Arseniy Krasnov
2022-11-21 15:28   ` Stefano Garzarella
2022-11-21 16:51     ` Arseniy Krasnov

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=ba294dff-812a-bfc2-a43c-286f99aee0b8@sberdevices.ru \
    --to=avkrasnov@sberdevices.ru \
    --cc=bobby.eshleman@gmail.com \
    --cc=kernel@sberdevices.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oxffffaa@gmail.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®