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 20FE2423C0; Fri, 13 Jan 2023 09:12:24 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0CBFC410EF; Fri, 13 Jan 2023 09:12:24 +0100 (CET) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) by mails.dpdk.org (Postfix) with ESMTP id C6F02410D4 for ; Fri, 13 Jan 2023 09:12:22 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id EC9653200909; Fri, 13 Jan 2023 03:12:20 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 13 Jan 2023 03:12:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1673597540; x= 1673683940; bh=S5+h+IC4aYH9uWKTCmOB4r+zL0Ye9vgeBa5eZVIeR0A=; b=b rsDO1BeSV4L3wUMebDiSWEM8DRNoe93oKlxz77NWqhYk5KaaiGwfwSr7uuINDtYZ MuSNoSRnUVxfMbqH2eb9ZHxlNcewA7SNOaxC0Ly4DGISUnF2riGwXw/1w1AAK0rf zhc67o/XnUU/IbqnXveewsvEqWfL+9Emg9wMFmM1EdjNr4d8ItunSukZ6lzekJT4 eZYmUzCegNvu6wExrb2YSpVJlaF2qejAzcHRsV4ZPGfch9Ph1zSvPikhpt/nKGhY strI59HOuXQ4IaPhTVqaE3c27YeJXEqeIUDscAZWZsf8hogWyS8u8YAJ6Bxpg8gG IPkARigprPYZp5wOk2G8A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1673597540; x= 1673683940; bh=S5+h+IC4aYH9uWKTCmOB4r+zL0Ye9vgeBa5eZVIeR0A=; b=L dZVTH7ogKzlJqr07jcq7R6vaKtMR79xb02CBDMKXwTUyLNPk7w8Fo2atB0zb/uB+ KbUoJTytUNNSeO9FOByhtF/9P6RJU227RXJ8WiilwZW/XrRXSXqxc2ZVSD7t26Hl qHGTTSSYc7m2ldMEJDA0iSfyvSaK3FTi961GcT0d+bnE44oBjjT0BzrnmFyv/ptB 8lpKJSrqwbJ10iJt9kiz0vi+Rs0Uiu7j/+gwdrCwf34JTx4OWcMFk4RE8lg3Tjhb lxMyDWMkWzYan3FCekmIDpxJWMEhkb5I6V/K0aV2rVhSx7QL1ro3JQpZpjeEVQh8 TPxTuTfPDWL/RNfWs6eWg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrleejgdduudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpedtjeeiieefhedtfffgvdelteeufeefheeujefgueetfedttdei kefgkeduhedtgfenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 13 Jan 2023 03:12:19 -0500 (EST) From: Thomas Monjalon To: Stephen Hemminger Cc: dev@dpdk.org, Cristian Dumitrescu , Bruce Richardson , Anatoly Burakov Subject: Re: [RFC] Remove Kernel Network Interface (KNI) Date: Fri, 13 Jan 2023 09:12:16 +0100 Message-ID: <2383172.OBFZWjSADL@thomas> In-Reply-To: <20230113050313.87378-1-stephen@networkplumber.org> References: <20230113050313.87378-1-stephen@networkplumber.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 13/01/2023 06:03, Stephen Hemminger: > The Linux special network driver for kernel networking has been > a long term problem for DPDK. The performance benefits of KNI > are available via virtio-user and XDP, and the simpler kernel > interface via TAP is also available. > > This driver has required lots of effort to keep up with the > kernel API changes. And the overall architecture of the driver > is fundamentally insecure and has unfixable locking and data > race problems. No developer has been willing to do extensive > tests or be the maintainer. > > In short, the time has come to do some early spring cleaning > and remove KNI from DPDK 23.03. In doc/guides/rel_notes/deprecation.rst it is announced to be removed in 23.11. Let's keep this RFC for later :)