From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ua0-f178.google.com (mail-ua0-f178.google.com [209.85.217.178]) by dpdk.org (Postfix) with ESMTP id 245C95A3E for ; Tue, 13 Jun 2017 20:00:17 +0200 (CEST) Received: by mail-ua0-f178.google.com with SMTP id q15so80440033uaa.2 for ; Tue, 13 Jun 2017 11:00:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infinite-io.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=f/ExnslFMsCKy+mZS4Luvi3FPN923ugPRBgvt3trDe0=; b=Bo3Cn4pXVK4I351/UgTdQIt5K1TO6zEQb1oUkib1Abs/YhOctm4exgLPYvOBntoQdk s3N1TpASxbb0sgpBrEFvkkflILraDHE6VaV1h2onYPwdeHkwYfOgMZuxQDKQpNGTgBAA u59YMEaULO7/ONegg3xs7K97Qr7gi2exL3KicHvL2HqTkTuDfljSyoqtQ9his5E4w/Vd uLXfogZ9GI1Fl4Kq3lAyQYHOvpce+ztVtU/FDbhX3JeFR/hjxNiidMg8eT4UhzZ0ZHcV LWQ2K1VEl0NSG++2jVtV8RqC+WykW6muma9w635Ybh65d1zSZitkaTJG0pv9gmRfYWIa W7jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=f/ExnslFMsCKy+mZS4Luvi3FPN923ugPRBgvt3trDe0=; b=seWDaqjEvrlAfR+nE0ks0y5PviC4TsGIIkGUyT3rgfOI+VasbHBwWToV5AWplB38h/ 5Ot8WEjxgywWfiyfPdX9tu8mXiGOf3mKKpkA8f6G0UczJP/S+YSY6mrhYOqKjBrLr48L hqSp9qn8rTGwQyn+AdA7avdoH+Wnt4fvXW7cz26UtPKKqU+vk0zhtLKJqgN1OebFHuZf k0kgvrifLYWT2fu73F7SGfxnESqaZ5ZdzEbi8zH1nPzSVNAiGrAfOS4nXCp6aLFON3me 315ef0NCfSD3oMV079ibzNsgO8YqkgCMGUeZI9TyARIaZKm1uWlkEy28Vn4qXYb87wfI RrVQ== X-Gm-Message-State: AKS2vOxs5S2xf+3JCN3bEbapaJFUzEFZ8IOhsO4vojiXwYCIQn2NmGeO a5Qo9Ned6bzQQk8HKX3SAziYqVjP0hzQ X-Received: by 10.176.27.151 with SMTP id k23mr3275323uai.151.1497376817311; Tue, 13 Jun 2017 11:00:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.99.193 with HTTP; Tue, 13 Jun 2017 11:00:16 -0700 (PDT) In-Reply-To: References: <20170526165228.96919-1-ferruh.yigit@intel.com> <3497879.P1UMQ6Rz4g@xps> From: Jay Rolette Date: Tue, 13 Jun 2017 13:00:16 -0500 Message-ID: To: Ferruh Yigit Cc: Thomas Monjalon , DPDK Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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, 13 Jun 2017 18:00:18 -0000 On Tue, Jun 13, 2017 at 12:21 PM, Ferruh Yigit wrote: > On 5/30/2017 11:55 AM, Thomas Monjalon wrote: > > 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. > > That is the intention with this feature. > > > > > Anyway, do you think KCP (or NCI) could be upstreamed in any way? > > Unfortunately I believe the answer is same, it may not be possible to > upsteam this kernel module. Should this fact block the feature? > Upstream is better, but KCP is a nice quality-of-life feature that I'd like to see go in regardless. Anything that helps make DPDK less "foreign" to normal port configuration and status tools is goodness. Jay