From: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
To: Paolo Abeni <pabeni@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Krasnov Arseniy <oxffffaa@gmail.com>,
"Bobby Eshleman" <bobby.eshleman@bytedance.com>,
kernel <kernel@sberdevices.ru>
Subject: Re: [PATCH net-next v7 4/4] test/vsock: vsock_perf utility
Date: Thu, 12 Jan 2023 11:55:41 +0000 [thread overview]
Message-ID: <678816e6-9480-a0d3-4aca-23e58013dbc6@sberdevices.ru> (raw)
In-Reply-To: <455b49a98c98edb1512ba2365adc76ac78a2b71b.camel@redhat.com>
On 12.01.2023 14:53, Paolo Abeni wrote:
> On Tue, 2023-01-10 at 10:18 +0000, Arseniy Krasnov wrote:
>> This adds utility to check vsock rx/tx performance.
>>
>> Usage as sender:
>> ./vsock_perf --sender <cid> --port <port> --bytes <bytes to send>
>> Usage as receiver:
>> ./vsock_perf --port <port> --rcvlowat <SO_RCVLOWAT>
>>
>> Signed-off-by: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
>> ---
>> tools/testing/vsock/Makefile | 3 +-
>> tools/testing/vsock/README | 34 +++
>> tools/testing/vsock/vsock_perf.c | 427 +++++++++++++++++++++++++++++++
>> 3 files changed, 463 insertions(+), 1 deletion(-)
>> create mode 100644 tools/testing/vsock/vsock_perf.c
>>
>> diff --git a/tools/testing/vsock/Makefile b/tools/testing/vsock/Makefile
>> index f8293c6910c9..43a254f0e14d 100644
>> --- a/tools/testing/vsock/Makefile
>> +++ b/tools/testing/vsock/Makefile
>> @@ -1,8 +1,9 @@
>> # SPDX-License-Identifier: GPL-2.0-only
>> -all: test
>> +all: test vsock_perf
>> test: vsock_test vsock_diag_test
>> vsock_test: vsock_test.o timeout.o control.o util.o
>> vsock_diag_test: vsock_diag_test.o timeout.o control.o util.o
>> +vsock_perf: vsock_perf.o
>>
>> CFLAGS += -g -O2 -Werror -Wall -I. -I../../include -I../../../usr/include -Wno-pointer-sign -fno-strict-overflow -fno-strict-aliasing -fno-common -MMD -U_FORTIFY_SOURCE -D_GNU_SOURCE
>> .PHONY: all test clean
>> diff --git a/tools/testing/vsock/README b/tools/testing/vsock/README
>> index 4d5045e7d2c3..84ee217ba8ee 100644
>> --- a/tools/testing/vsock/README
>> +++ b/tools/testing/vsock/README
>> @@ -35,3 +35,37 @@ Invoke test binaries in both directions as follows:
>> --control-port=$GUEST_IP \
>> --control-port=1234 \
>> --peer-cid=3
>> +
>> +vsock_perf utility
>> +-------------------
>> +'vsock_perf' is a simple tool to measure vsock performance. It works in
>> +sender/receiver modes: sender connect to peer at the specified port and
>> +starts data transmission to the receiver. After data processing is done,
>> +it prints several metrics(see below).
>> +
>> +Usage:
>> +# run as sender
>> +# connect to CID 2, port 1234, send 1G of data, tx buf size is 1M
>> +./vsock_perf --sender 2 --port 1234 --bytes 1G --buf-size 1M
>> +
>> +Output:
>> +tx performance: A Gbits/s
>> +
>> +Output explanation:
>> +A is calculated as "number of bits to send" / "time in tx loop"
>> +
>> +# run as receiver
>> +# listen port 1234, rx buf size is 1M, socket buf size is 1G, SO_RCVLOWAT is 64K
>> +./vsock_perf --port 1234 --buf-size 1M --vsk-size 1G --rcvlowat 64K
>> +
>> +Output:
>> +rx performance: A Gbits/s
>> +total in 'read()': B sec
>> +POLLIN wakeups: C
>> +average in 'read()': D ns
>> +
>> +Output explanation:
>> +A is calculated as "number of received bits" / "time in rx loop".
>> +B is time, spent in 'read()' system call(excluding 'poll()')
>> +C is number of 'poll()' wake ups with POLLIN bit set.
>> +D is B / C, e.g. average amount of time, spent in single 'read()'.
>> diff --git a/tools/testing/vsock/vsock_perf.c b/tools/testing/vsock/vsock_perf.c
>> new file mode 100644
>> index 000000000000..a72520338f84
>> --- /dev/null
>> +++ b/tools/testing/vsock/vsock_perf.c
>> @@ -0,0 +1,427 @@
>> +// SPDX-License-Identifier: GPL-2.0-only
>> +/*
>> + * vsock_perf - benchmark utility for vsock.
>> + *
>> + * Copyright (C) 2022 SberDevices.
>> + *
>> + * Author: Arseniy Krasnov <AVKrasnov@sberdevices.ru>
>> + */
>> +#include <getopt.h>
>> +#include <stdio.h>
>> +#include <stdlib.h>
>> +#include <stdbool.h>
>> +#include <string.h>
>> +#include <errno.h>
>> +#include <unistd.h>
>> +#include <time.h>
>> +#include <stdint.h>
>> +#include <poll.h>
>> +#include <sys/socket.h>
>> +#include <linux/vm_sockets.h>
>> +
>> +#define DEFAULT_BUF_SIZE_BYTES (128 * 1024)
>> +#define DEFAULT_TO_SEND_BYTES (64 * 1024)
>> +#define DEFAULT_VSOCK_BUF_BYTES (256 * 1024)
>> +#define DEFAULT_RCVLOWAT_BYTES 1
>> +#define DEFAULT_PORT 1234
>> +
>> +#define BYTES_PER_GB (1024 * 1024 * 1024ULL)
>> +#define NSEC_PER_SEC (1000000000ULL)
>> +
>> +static unsigned int port = DEFAULT_PORT;
>> +static unsigned long buf_size_bytes = DEFAULT_BUF_SIZE_BYTES;
>> +static unsigned long vsock_buf_bytes = DEFAULT_VSOCK_BUF_BYTES;
>> +
>> +static void error(const char *s)
>> +{
>> + perror(s);
>> + exit(EXIT_FAILURE);
>> +}
>
> For the records, I suggested to use the existing error() libcall, see
> man 3 error.
>
> Not a big deal. This can be merged as-is, and you can follow-up, it you
> find it useful.
Ahhhhh, I see, thanks!
Thanks, Arseniy
>
> Cheers,
>
> Paolo
>
next prev parent reply other threads:[~2023-01-12 12:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 10:11 [PATCH net-next v7 0/4] vsock: update tools and error handling Arseniy Krasnov
2023-01-10 10:13 ` [PATCH net-next v7 1/4] vsock: return errors other than -ENOMEM to socket Arseniy Krasnov
2023-01-10 10:15 ` [PATCH net-next v7 2/4] test/vsock: rework message bounds test Arseniy Krasnov
2023-01-10 10:17 ` [PATCH net-next v7 3/4] test/vsock: add big message test Arseniy Krasnov
2023-01-10 10:18 ` [PATCH net-next v7 4/4] test/vsock: vsock_perf utility Arseniy Krasnov
2023-01-11 8:30 ` Stefano Garzarella
2023-01-12 11:53 ` Paolo Abeni
2023-01-12 11:55 ` Arseniy Krasnov [this message]
2023-01-12 12:10 ` [PATCH net-next v7 0/4] vsock: update tools and error handling patchwork-bot+netdevbpf
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=678816e6-9480-a0d3-4aca-23e58013dbc6@sberdevices.ru \
--to=avkrasnov@sberdevices.ru \
--cc=bobby.eshleman@bytedance.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel@sberdevices.ru \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oxffffaa@gmail.com \
--cc=pabeni@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®