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 9EDEF45E79; Wed, 11 Dec 2024 16:03:57 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 260A84026E; Wed, 11 Dec 2024 16:03:57 +0100 (CET) Received: from mail-pf1-f176.google.com (mail-pf1-f176.google.com [209.85.210.176]) by mails.dpdk.org (Postfix) with ESMTP id 6247C40267 for ; Wed, 11 Dec 2024 16:03:55 +0100 (CET) Received: by mail-pf1-f176.google.com with SMTP id d2e1a72fcca58-7273967f2f0so2983202b3a.1 for ; Wed, 11 Dec 2024 07:03:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1733929434; x=1734534234; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=zbmQnRYP/kX87lkRvH3NZo6pOlIgLb0/u2gGeWTCKcs=; b=vNLwP4aeyBfRkt0UZYxNGw5wZgIHtJnL9rMxRKJxWz9FeEQdN76CL9f7iJC/9nG8O0 EyyxdR3siNDilGMFFOf1q5BZeYhbPUiJZFy2YpOd1BRZpneLORAKbNmPg3ITTedZ+N/5 FB5O7b+yJY/0G/+34fJPNYbkUZrPcJnLqPPb4gmGqnLtgohtJUZNzi+I/OsNgP7oLj8q AbW4N05ST7G8UOv5dlYhRDZAK8GuXP/BrWp3q9uLy8+J7G4ocJRUMwBMqRtyB0NAdI2Q 1XvPPmnZWO4tbO/BLZ7uMdm/FltbomGmkpODl6iekhu5uXlRIeFCQSan1EipZtBwLMO5 kuQg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733929434; x=1734534234; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=zbmQnRYP/kX87lkRvH3NZo6pOlIgLb0/u2gGeWTCKcs=; b=PYnZzWSSvqc3sRLR3sCa74O4svGmt6e5mHhn8ugKox0kDZ2ffv/Q0Bw+G4afZrRYu7 YzlYRgiftyuUJROqtFwYKHEU7q4aql/d8x/rB2QkRTYSs4CkS4LI8UTvQbgu5LUpcWGj At/ZaPPLhq44OSFUARb7K08JD3SJuRPZ5mX0Z7meymGu1cKtzhkgxGrUCboLPJrtrM5f EM5AbJldhSLC4XiXl1yExI/JbjaJZ617kXgiM8URYWP7lcO/AvP7Ol9ny9Gn4CrrZUq9 OZOZo7+Jg0p1bV0quaXcBd/MDyDC3ZmXc1UbNC2pdUvbB5DNP4c2NEhsA6TIrnUxk2Bt FbeA== X-Gm-Message-State: AOJu0Yx4rD5dukfL4LJjb/O61qVS+qEnuctT7gIBFTXwKh5SSkdY1uLm giR6BHF/aW7XTSbIQtFNAHHUtQcfIsKLZc+Mr6blVdxmKEhZjQ4p9VJUPtQf7bU= X-Gm-Gg: ASbGncuCDd61PtpWA9B2lxEVX9lKLw22xKLZ7df4aAHxP10IeRr/w0thIHP9GWoCBdB ZMNxhvlsmPPkLygnAa3n8L3LgvuepdtsLO8aYL2QEwoI1xNBlrry+ZrP2ixm4s2kDVSvyXgR8XN O5m+dDshCEgAdVnuQ3chNGB8Vkia1JSjxGOXYYTCiAmH6kn04jXJfu0rFeCGWqfK5ABiTexscpg FCzMvvD4VyckBdoK/xn9NyCli0YhYbPJkABqFD5i409HnqEExm9zEg+92rLhW03+iKgXzkTjSIp HtJWj5ODZxsX9nFygVnzSnoh93VIE94I/A== X-Google-Smtp-Source: AGHT+IH3yJufVLtSvoA8mJ+MxrExC7Pf1IsytmNdZdt3zZU+SAzK3aMPAAcOa1hpaAbkvUq1FSsG7Q== X-Received: by 2002:a05:6a00:3e07:b0:725:f376:f4ff with SMTP id d2e1a72fcca58-728ed3e8716mr5222131b3a.13.1733929434490; Wed, 11 Dec 2024 07:03:54 -0800 (PST) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-725d251137bsm7964702b3a.62.2024.12.11.07.03.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 11 Dec 2024 07:03:54 -0800 (PST) Date: Wed, 11 Dec 2024 07:03:52 -0800 From: Stephen Hemminger To: Konstantin Ananyev Cc: "dev@dpdk.org" Subject: Re: [RFC 0/8] ioring: network driver Message-ID: <20241211070352.6d32e332@hermes.local> In-Reply-To: References: <20241210212757.83490-1-stephen@networkplumber.org> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 On Wed, 11 Dec 2024 11:34:39 +0000 Konstantin Ananyev wrote: > > 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. There are some userspaces that look for "e*" in name for some setups. But names are totally abitrary