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 CCC7445EFA; Fri, 20 Dec 2024 15:34:29 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 937F840144; Fri, 20 Dec 2024 15:34:29 +0100 (CET) Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) by mails.dpdk.org (Postfix) with ESMTP id 440F04003C for ; Fri, 20 Dec 2024 15:34:28 +0100 (CET) Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4YF90X3j3Yz6K6ld; Fri, 20 Dec 2024 22:34:20 +0800 (CST) Received: from frapeml500006.china.huawei.com (unknown [7.182.85.219]) by mail.maildlp.com (Postfix) with ESMTPS id 8887D140A46; Fri, 20 Dec 2024 22:34:27 +0800 (CST) Received: from frapeml500007.china.huawei.com (7.182.85.172) by frapeml500006.china.huawei.com (7.182.85.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.39; Fri, 20 Dec 2024 15:34:27 +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; Fri, 20 Dec 2024 15:34:27 +0100 From: Konstantin Ananyev To: =?iso-8859-1?Q?Morten_Br=F8rup?= , "Stephen Hemminger" CC: "dev@dpdk.org" Subject: RE: [RFC 0/8] ioring: network driver Thread-Topic: [RFC 0/8] ioring: network driver Thread-Index: AQHbS0qCt0bW2Ou+h0Wq0GfJ/VNsu7Lg6iHAgAAqTgCAAeZQwIAKxhZQgAGAeKA= Date: Fri, 20 Dec 2024 14:34:27 +0000 Message-ID: References: <20241210212757.83490-1-stephen@networkplumber.org> <20241211070352.6d32e332@hermes.local> <3426021bf73d4e42bbe35597976a2d85@huawei.com> <98CBD80474FA8B44BF855DF32C47DC35E9F969@smartserver.smartshare.dk> In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F969@smartserver.smartshare.dk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.81.196.212] Content-Type: text/plain; charset="iso-8859-1" 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 > > From: Konstantin Ananyev [mailto:konstantin.ananyev@huawei.com] > > > > > > > This is first draft of new simplified TAP device that uses > > > > > the Linux kernel ioring API to provide a read/write ring > > > > > with kernel. > > > > > > > > > > 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. > > > > > > > > > > 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 > > > > and might be confusing. >=20 > Konstantin is referring to the name of the driver and the source code fil= e names, "net/ioring" -> "net/tap_ioring". Yep, that what I meant. >=20 > > > > > > There are some userspaces that look for "e*" in name for some setups. >=20 > Stephen is referring to the device name of an instantiated interface, e.g= . "eth0". >=20 > And yes, assuming devices named "e*" are Ethernet devices is a common hac= k in Linux applications. I've done it myself. :-) Ok... and why such practice should prevent us to name PMD itself in a way w= e think is appropriate?=20 =20 > > > > Didn't get you here, pls try to re-phrase. > > > > > But names are totally arbitrary >=20 >=20