From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [PATCH v5 0/4] Use common Linux tools to control
 DPDK ports
Date: Tue, 15 Mar 2016 00:00:43 +0000
Message-ID: <56E750AB.3040707@intel.com>
References: <1456846920-28770-1-git-send-email-ferruh.yigit@intel.com>
 <1457523689-6223-1-git-send-email-ferruh.yigit@intel.com>
 <56E6D956.8050809@intel.com>
 <CADNuJVpr_0eOj8KW1fH5_-ed-6=si-Xsgjffcitd5CtVA8Qz9Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: DPDK <dev@dpdk.org>, David Marchand <david.marchand@6wind.com>,
 Helin Zhang <helin.zhang@intel.com>, Remy Horton <remy.horton@intel.com>
To: Jay Rolette <rolette@infiniteio.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga01.intel.com (mga01.intel.com [192.55.52.88])
 by dpdk.org (Postfix) with ESMTP id 82EA85320
 for <dev@dpdk.org>; Tue, 15 Mar 2016 01:00:47 +0100 (CET)
In-Reply-To: <CADNuJVpr_0eOj8KW1fH5_-ed-6=si-Xsgjffcitd5CtVA8Qz9Q@mail.gmail.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 3/14/2016 5:40 PM, Jay Rolette wrote:
> Is there some technical reason or is it just the push-back you are
> getting from some of the maintainers?
>=20
The majority of the discussion on the list was based on not having
kernel modules, which cloud the desired technical discussion.

As a result of the opposition, we will give a try to upstreaming and I
will be able to use some of my time to work on this.

If KCP can be upstreamed, this is good for everybody, if not I hope we
can discuss again in community the future of the feature.

And during this process, userspace counterpart in DPDK will be missing,
and kernel part will be in a form of patch for head of latest kernel, so
not sure how community will be able to test this.

> I chimed in on one of the other threads already, but I'm extremely
> disappointed that usability and serviceability improvements to existing
> DPDK capabilities (KNI) are getting blocked like this.
>=20
> For companies building network appliances based on DPDK, having a kerne=
l
> module that isn't in the tree just isn't that big of a deal. Long term
> goals for getting this upstream are great, but why not take advantage o=
f
> incremental improvements in the meantime?
>=20
> Jay=20
>=20
> On Mon, Mar 14, 2016 at 10:31 AM, Ferruh Yigit <ferruh.yigit@intel.com
> <mailto:ferruh.yigit@intel.com>> wrote:
>=20
>     On 3/9/2016 11:41 AM, Ferruh Yigit wrote:
>     > This patch sent to keep record of latest status of the work.
>     >
>     >
>     > This work is to make DPDK ports more visible and to enable using =
common
>     > Linux tools to configure DPDK ports.
>     >
>     > Patch is based on KNI but contains only control functionality of =
it,
>     > also this patch does not include any Linux kernel network driver =
as
>     > part of it.
>     >
>     > Basically with the help of a kernel module (KCP), virtual Linux n=
etwork
>     > interfaces named as "dpdk$" are created per DPDK port, control me=
ssages
>     > sent to these virtual interfaces are forwarded to DPDK, and respo=
nse
>     > sent back to Linux application.
>     >
>     > Virtual interfaces created when DPDK application started and dest=
royed
>     > automatically when DPDK application terminated.
>     >
>     > Communication between kernel-space and DPDK done using netlink so=
cket.
>     >
>     > In long term this patch intends to replace the KNI and KNI will b=
e
>     > depreciated.
>     >
>=20
>     Self-NACK: Will work on netdev to upstream this.
>=20
>=20