From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id E378945E77; Wed, 11 Dec 2024 12:34:43 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A5D6C4026E; Wed, 11 Dec 2024 12:34:42 +0100 (CET) Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) by mails.dpdk.org (Postfix) with ESMTP id 3C729400D7 for ; Wed, 11 Dec 2024 12:34:41 +0100 (CET) Received: from mail.maildlp.com (unknown [172.18.186.231]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Y7YL26QxXz6GC3g; Wed, 11 Dec 2024 19:30:02 +0800 (CST) Received: from frapeml100007.china.huawei.com (unknown [7.182.85.133]) by mail.maildlp.com (Postfix) with ESMTPS id 1B8AA1400DD; Wed, 11 Dec 2024 19:34:40 +0800 (CST) Received: from frapeml500007.china.huawei.com (7.182.85.172) by frapeml100007.china.huawei.com (7.182.85.133) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Wed, 11 Dec 2024 12:34:39 +0100 Received: from frapeml500007.china.huawei.com ([7.182.85.172]) by frapeml500007.china.huawei.com ([7.182.85.172]) with mapi id 15.01.2507.039; Wed, 11 Dec 2024 12:34:39 +0100 From: Konstantin Ananyev To: Stephen Hemminger , "dev@dpdk.org" Subject: RE: [RFC 0/8] ioring: network driver Thread-Topic: [RFC 0/8] ioring: network driver Thread-Index: AQHbS0qCt0bW2Ou+h0Wq0GfJ/VNsu7Lg6iHA Date: Wed, 11 Dec 2024 11:34:39 +0000 Message-ID: References: <20241210212757.83490-1-stephen@networkplumber.org> In-Reply-To: <20241210212757.83490-1-stephen@networkplumber.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.206.138.73] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org > This is first draft of new simplified TAP device that uses > the Linux kernel ioring API to provide a read/write ring > with kernel. >=20 > This is split from tap device because there are so many > unnecessary things in existing tap, and supporting ioring is > better without ifdefs etc. The default name of the tap > device is different that other uses in DPDK but the driver > tries to keep the same relevant devargs as before. >=20 > This driver will only provide features that match what kernel > does, so no flow support etc. The next version will add checksum > and multi-segment packets. Some of the doc files may need update > as well. Makes sense to me, though didn't properly look inside. One thing - probably add a 'tap' into the name, 'tap_ioiring' or so, otherwise 'ioring' is a bit too generic=20 and might be confusing. > Stephen Hemminger (8): > net/ioring: introduce new driver > net/ioring: implement link state > net/ioring: implement control functions > net/ioring: implement management functions > net/ioring: implement primary secondary fd passing > net/ioring: implement receive and transmit > net/ioring: add VLAN support > net/ioring: implement statistics >=20 > doc/guides/nics/features/ioring.ini | 14 + > doc/guides/nics/index.rst | 1 + > doc/guides/nics/ioring.rst | 66 ++ > drivers/net/ioring/meson.build | 12 + > drivers/net/ioring/rte_eth_ioring.c | 1067 +++++++++++++++++++++++++++ > drivers/net/meson.build | 1 + > 6 files changed, 1161 insertions(+) > create mode 100644 doc/guides/nics/features/ioring.ini > create mode 100644 doc/guides/nics/ioring.rst > create mode 100644 drivers/net/ioring/meson.build > create mode 100644 drivers/net/ioring/rte_eth_ioring.c >=20 > -- > 2.45.2