From patchwork Sun Jan 8 20:35:18 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Arseniy Krasnov X-Patchwork-Id: 3711 Return-Path: Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:4e01:0:0:0:0:0 with SMTP id p1csp1843851wrt; Sun, 8 Jan 2023 12:39:37 -0800 (PST) X-Google-Smtp-Source: AMrXdXvI5ugsWrlXaU9a6/g+dXTXlLoAOojLhWYkGUAi0w+w1cPHE4E1ccl9BkUGTM3CTZFNhpZu X-Received: by 2002:aa7:955d:0:b0:582:d5e3:12a7 with SMTP id w29-20020aa7955d000000b00582d5e312a7mr21317774pfq.6.1673210376988; Sun, 08 Jan 2023 12:39:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673210376; cv=none; d=google.com; s=arc-20160816; b=W8TqcO+qq1tI0EhjGufJwQQ9qduw55i9CnL3MdOcj1PX2rOB3db3Am0fF/QyYI8FHk WOzd0aCbZy2NggNn4zLlX3BKujf1DWZtAC133TOnnd9gRECZviIl28d+44S/r5X+LWFd IMZprow0pyIvi4kGL2CnPOMbf9K99VIE80IIGVDM6CN1uwRy2UHoH88R8xHyOCxHfbjs CCBq6VOQ2uiLoJPC3b/obNpbwEQULdmWBeH1CL89I8FmvQukBZlawne73Jw4U+VLDh2i RTHAdG3MrNxKNthAQEHr4ncB47NxBORWJ0jpVfTLFUkdIltXZ2rUP4zGl7Z9ZG0pefH/ Y0aw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:content-transfer-encoding :content-id:content-language:accept-language:message-id:date :thread-index:thread-topic:subject:cc:to:from:dkim-signature; bh=TCq52kcKV/J4zSTRILhb+Ziq3T6/w8ItLE2NuTjw30w=; b=moeUk0GybrVRXW/pYWVOFV2JRmtjiauQL6e8w1O0vla4+SButRYBkRusd850Pwwkvl 4olJdgSqs0bUCreGEvAhTCA1+GLEXzsMU0FMMQJbY+1+06ELpfPQ2D2fjipGA+qbz2N+ 2kJMPdh5g6PmiiewpZXD04Bjt9d/NbIVb4/WKC1CIRA0p9VAKCm/Xsb+bVpUhpVhmCv8 6MU9cesmxhOmgbMercYs8SzOSm8JQoz72A5y8yUme0VfQcdeh87bYyOcsBYq/zTKXp+G 7RPUeqzKUqjiLgCt8xMub+qAfBXXo5Z5wdvNDAUtwaWoyk4mZ3U1kjO9lkxRZPFNseLT V6aw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sberdevices.ru header.s=mail header.b=gFFaTQCS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=sberdevices.ru Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id p18-20020a62ab12000000b00580f3360e15si7354884pff.110.2023.01.08.12.39.24; Sun, 08 Jan 2023 12:39:36 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@sberdevices.ru header.s=mail header.b=gFFaTQCS; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=sberdevices.ru Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233647AbjAHUfd (ORCPT + 99 others); Sun, 8 Jan 2023 15:35:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43702 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233243AbjAHUfb (ORCPT ); Sun, 8 Jan 2023 15:35:31 -0500 Received: from mx.sberdevices.ru (mx.sberdevices.ru [45.89.227.171]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4B69AB4BD; Sun, 8 Jan 2023 12:35:26 -0800 (PST) Received: from s-lin-edge02.sberdevices.ru (localhost [127.0.0.1]) by mx.sberdevices.ru (Postfix) with ESMTP id 775015FD02; Sun, 8 Jan 2023 23:35:22 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sberdevices.ru; s=mail; t=1673210122; bh=TCq52kcKV/J4zSTRILhb+Ziq3T6/w8ItLE2NuTjw30w=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=gFFaTQCSMMwWV2uZbPn2P7rdZLGBs6ravZ1KMbI1lK0Ug4iH9ybDog5vJWEz0GVGD qhX6NG7q0Q4tHiSyVc4Dzovyt3Zbc+5SiDVHQb756ltzZmBsR44M98JpCOXaN/ApYS zHfTZCZ+oLJ7U8rj0VE8dafNPGAiyRBdlklY45G7DcdrCT8LD8lflWN28K9hrb/EVf xeS2c2DSiNWxhvLY177MFZVECCUt4CoD4e1D10ogNnWVaiGVFoKcsjuc1s16+cCeJL qfEs3wZABmH1LZT6tZaPqqsICMoKdpRjxDTQEFM+ps5vyz1y1GuPTSobf7I2uGijYy iLvr6na5pSfXw== Received: from S-MS-EXCH01.sberdevices.ru (S-MS-EXCH01.sberdevices.ru [172.16.1.4]) by mx.sberdevices.ru (Postfix) with ESMTP; Sun, 8 Jan 2023 23:35:19 +0300 (MSK) From: Arseniy Krasnov To: Stefano Garzarella , "David S. Miller" , "edumazet@google.com" , "Paolo Abeni" , Jakub Kicinski CC: "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" , "virtualization@lists.linux-foundation.org" , kernel , Bobby Eshleman , Krasnov Arseniy , Arseniy Krasnov Subject: [PATCH net-next v6 0/4] vsock: update tools and error handling Thread-Topic: [PATCH net-next v6 0/4] vsock: update tools and error handling Thread-Index: AQHZI6C4l/Z0Y69LvkeRvu+gUqG55w== Date: Sun, 8 Jan 2023 20:35:18 +0000 Message-ID: <9ad41d2b-bbe9-fe55-3aba-6a1281b6aa1b@sberdevices.ru> Accept-Language: en-US, ru-RU Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.1.12] Content-ID: <345230C68B50354A937D4AE2EC5F3B85@sberdevices.ru> MIME-Version: 1.0 X-KSMG-Rule-ID: 4 X-KSMG-Message-Action: clean X-KSMG-AntiSpam-Status: not scanned, disabled by settings X-KSMG-AntiSpam-Interceptor-Info: not scanned X-KSMG-AntiPhishing: not scanned, disabled by settings X-KSMG-AntiVirus: Kaspersky Secure Mail Gateway, version 1.1.2.30, bases: 2023/01/08 17:38:00 #20747751 X-KSMG-AntiVirus-Status: Clean, skipped X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1754488244285781214?= X-GMAIL-MSGID: =?utf-8?q?1754488244285781214?= Patchset consists of two parts: 1) Kernel patch One patch from Bobby Eshleman. I took single patch from Bobby: https://lore.kernel.org/lkml/d81818b868216c774613dd03641fcfe63cc55a45 .1660362668.git.bobby.eshleman@bytedance.com/ and use only part for af_vsock.c, as VMCI and Hyper-V parts were rejected. I used it, because for SOCK_SEQPACKET big messages handling was broken - ENOMEM was returned instead of EMSGSIZE. And anyway, current logic which always replaces any error code returned by transport to ENOMEM looks strange for me also(for example in EMSGSIZE case it was changed to ENOMEM). 2) Tool patches 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'/'uperf', because: 1) It is small comparing to 'iperf' or 'uperf', so it very easy to add new mode or feature to it(especially vsock specific). 2) It allows to set SO_RCVLOWAT and SO_VM_SOCKETS_BUFFER_SIZE option. Whole throughtput depends on both parameters. 3) It is located in the 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). Here is comparison of outputs from three utils: 'iperf', 'uperf' and 'vsock_perf'. In all three cases sender was at guest side. rx and tx buffers were always 64Kb(because by default 'uperf' uses 8K). iperf: [ ID] Interval Transfer Bitrate [ 5] 0.00-10.00 sec 12.8 GBytes 11.0 Gbits/sec sender [ 5] 0.00-10.00 sec 12.8 GBytes 11.0 Gbits/sec receiver uperf: Total 16.27GB / 11.36(s) = 12.30Gb/s 23455op/s vsock_perf: tx performance: 12.301529 Gbits/s rx performance: 12.288011 Gbits/s Results are almost same in all three cases. Patchset was rebased and tested on skbuff v9 patch from Bobby Eshleman: https://lore.kernel.org/netdev/20230107002937.899605-1-bobby.eshleman@bytedance.com/ Changelog: v5 -> v6: - RFC -> net-next tag - vsock_perf: - forget to update README: Gb/s -> GBits/s v4 -> v5: - Kernel patch: update commit message - vsock_perf: - Fix typo in commit message - Use "fprintf(stderr," instead of "printf(" for errors - More stats for tx: total bytes sent and time in tx loop - Print throughput in 'gigabits' instead of 'gigabytes'(as in 'iperf' and 'uperf') - Output comparisons between 'iperf', 'uperf' and 'vsock_perf' added to CV. v3 -> v4: - Kernel patch: update commit message by adding error case description - Message bounds test: - Typo fix: s/contols/controls - Fix error output on 'setsockopt()'s - vsock_perf: - Add 'vsock_perf' target to 'all' in Makefile - Fix error output on 'setsockopt()'s - Swap sender/receiver roles: now sender does 'connect()' and sends data, while receiver accepts connection. - Update arguments names: s/mb/bytes, s/so_rcvlowat/rcvlowat - Update usage output and description in README v2 -> v3: - Patches for VMCI and Hyper-V were removed from patchset(commented by Vishnu Dasa and Dexuan Cui) - In message bounds test hash is computed from data buffer with random content(in v2 it was size only). This approach controls both data integrity and message bounds. - vsock_perf: - grammar fixes - only long parameters supported(instead of only short) v1 -> v2: - Three new patches from Bobby Eshleman to kernel part - Message bounds test: some refactoring and add comment to describe hashing purpose - Big message test: check 'errno' for EMSGSIZE and move new test to the end of tests array - vsock_perf: - update README file - add simple usage example to commit message - update '-h' (help) output - use 'stdout' for output instead of 'stderr' - use 'strtol' instead of 'atoi' Bobby Eshleman(1): vsock: return errors other than -ENOMEM to socket Arseniy Krasnov(3): test/vsock: rework message bound test test/vsock: add big message test test/vsock: vsock_perf utility net/vmw_vsock/af_vsock.c | 3 +- tools/testing/vsock/Makefile | 3 +- tools/testing/vsock/README | 34 +++ tools/testing/vsock/control.c | 28 +++ tools/testing/vsock/control.h | 2 + tools/testing/vsock/util.c | 13 ++ tools/testing/vsock/util.h | 1 + tools/testing/vsock/vsock_perf.c | 441 +++++++++++++++++++++++++++++++++++++++ tools/testing/vsock/vsock_test.c | 197 +++++++++++++++-- 9 files changed, 705 insertions(+), 17 deletions(-) --- 2.25.1