From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id EFB851E2F for ; Tue, 30 May 2017 12:55:12 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4CB9720BB9; Tue, 30 May 2017 06:55:12 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 30 May 2017 06:55:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=WkDXJQrAfdNgUis M5pbcUqbfmhiR1LADEDq9NvQaieE=; b=fhJv4ftlwyDcUqTbU+xC2AM7nZ1aKS9 E58VjPccWJYqqL7TI/K0Sz+CHQ4y4GfBIre8grfk/GkHF4i0ST1yN3BCkhKQ0kQT e0kj4sjRBYOLV2ve7bEFyljV1b1r56NLAr7uCSTVNiUxNu50iyy0Fnpjx4fAmMBb fxVgNnbMZW2M= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=WkDXJQrAfdNgUisM5pbcUqbfmhiR1LADEDq9NvQaieE=; b=rL7OS+hO CansMeqtios91s0hIakejgRfmG1sxufSbWEXKnz4Ox6Q/mRzJ3oSfyC7e7uK2bzI f+QTlnS33kX0K31VGG3oq8ef45HXpqPW5ctYbb0c/3gKcb1akTAFrRtr3khClmse zXy7Qx/Z2w5/1b98DbiM36N5REjomdWoz0czGPnxTqjh15UWc+SghDcEmAPppiuO Oa4bryMqtfVpeJ5RQ7rzxzZpuAF815NDl+VH7q4B6oES0iidA/qLq7Azh3b/DP83 aRthoSD80S7F3VSvz4HPaK11SVh9EknF7Iz0WF8so+XBbabPpHZTdd3TG5lVTm8S 5MUsUswixTG87w== X-ME-Sender: X-Sasl-enc: H/MBacDEya0V7kVbEi2AThVbpWfY/ah0BiuJvMPRelOe 1496141712 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 05A5E2479C; Tue, 30 May 2017 06:55:12 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: dev@dpdk.org Date: Tue, 30 May 2017 12:55:11 +0200 Message-ID: <3497879.P1UMQ6Rz4g@xps> In-Reply-To: <20170526165228.96919-1-ferruh.yigit@intel.com> References: <20170526165228.96919-1-ferruh.yigit@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [RFC] Kernel Control Path (KCP) X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2017 10:55:13 -0000 26/05/2017 18:52, Ferruh Yigit: > We are looking for re-sending [1] the Kernel Control Path (KCP) > with some updates [2]. > > Mainly this is an usability improvement for DPDK. > > And a quick reminder about what KCP is: > > "KCP is Linux virtual network interface that can control DPDK ports". > > So DPDK interfaces, somehow will be visible and it will be possible to > use common Linux tools on DPDK interfaces. Reminder: the Mellanox PMDs live with their upstream kernel modules, allowing such features. The best model would be to have control path in kernel for every PMDs. Anyway, do you think KCP (or NCI) could be upstreamed in any way?