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 C556445EED; Thu, 19 Dec 2024 16:41:04 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5B3D540265; Thu, 19 Dec 2024 16:41:04 +0100 (CET) Received: from dkmailrelay1.smartsharesystems.com (smartserver.smartsharesystems.com [77.243.40.215]) by mails.dpdk.org (Postfix) with ESMTP id AE0894025F for ; Thu, 19 Dec 2024 16:41:02 +0100 (CET) Received: from smartserver.smartsharesystems.com (smartserver.smartsharesys.local [192.168.4.10]) by dkmailrelay1.smartsharesystems.com (Postfix) with ESMTP id 9EF2A20A77; Thu, 19 Dec 2024 16:41:01 +0100 (CET) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [RFC 0/8] ioring: network driver Date: Thu, 19 Dec 2024 16:40:58 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F969@smartserver.smartshare.dk> In-Reply-To: <3426021bf73d4e42bbe35597976a2d85@huawei.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [RFC 0/8] ioring: network driver Thread-Index: AQHbS0qCt0bW2Ou+h0Wq0GfJ/VNsu7Lg6iHAgAAqTgCAAeZQwIAKxhZQ References: <20241210212757.83490-1-stephen@networkplumber.org> <20241211070352.6d32e332@hermes.local> <3426021bf73d4e42bbe35597976a2d85@huawei.com> From: =?iso-8859-1?Q?Morten_Br=F8rup?= To: "Konstantin Ananyev" , "Stephen Hemminger" Cc: 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] >=20 > > > > 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. Konstantin is referring to the name of the driver and the source code = file names, "net/ioring" -> "net/tap_ioring". > > > > There are some userspaces that look for "e*" in name for some = setups. Stephen is referring to the device name of an instantiated interface, = e.g. "eth0". And yes, assuming devices named "e*" are Ethernet devices is a common = hack in Linux applications. I've done it myself. :-) >=20 > Didn't get you here, pls try to re-phrase. >=20 > > But names are totally arbitrary