From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH 1/3] kcp: add kernel control path kernel
	module
Date: Thu, 10 Mar 2016 01:04:48 +0100
Message-ID: <4528438.gG6caYbQZH@xps13>
References: <1453911849-16562-1-git-send-email-ferruh.yigit@intel.com>
 <2396478.VfdoPKd37H@xps13> <5360490.85HbqvIh1a@xps13>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Avi Kivity <avi@scylladb.com>, dev@dpdk.org
To: ferruh.yigit@intel.com
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53])
 by dpdk.org (Postfix) with ESMTP id 0776F2B98
 for <dev@dpdk.org>; Thu, 10 Mar 2016 01:06:36 +0100 (CET)
Received: by mail-wm0-f53.google.com with SMTP id p65so7410882wmp.0
 for <dev@dpdk.org>; Wed, 09 Mar 2016 16:06:36 -0800 (PST)
In-Reply-To: <5360490.85HbqvIh1a@xps13>
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>

2016-03-02 23:35, Thomas Monjalon:
> 2016-03-02 12:21, Thomas Monjalon:
> > 2016-03-02 11:47, Vincent JARDIN:
> > > Le 02/03/2016 09:27, Panu Matilainen a =E9crit :
> > > >>> I'd like to see these be merged.
> > > >>>
> > > >>> Jay
> > > >>
> > > >> The code is really not ready. I am okay with cooperative devel=
opment
> > > >> but the current code needs to go into a staging type tree.
> > > >> No compatibility, no ABI guarantees, more of an RFC.
> > > >> Don't want vendors building products with it then screaming wh=
en it
> > > >> gets rebuilt/reworked/scrapped.
> > > >>
> > > >
> > > > Exactly.
> > >=20
> > > +1 too
> > >=20
> > > We need to build on this innovation while there is a path for ker=
nel=20
> > > mainstream. The logic of using a staging is a good one.
> > >=20
> > > Thomas,
> > >=20
> > > can we open a staging folder into the DPDK like it is done into t=
he kernel?
> >=20
> > It's possible to create a staging directory if everybody agree.
> > It is important to state in a README file or in the doc/ that
> > there will be no guarantee (no stable ABI, no validation and can be=
 dropped)
> > and that it is a work in progress, a suggestion to discuss with the=
 kernel
> > community.
> >=20
> > The kernel modules must clearly target an upstream integration.
>=20
> Actually the examples directory has been used as a staging for ethtoo=
l and
> lthread. We also have the crypto API which is still experimental.
> So I think we must decide among these 3 solutions:
> =09- no special directory, just mark and document an experimental sta=
te
> =09- put only kcp/kdp in the staging directory
> =09- put kcp/kdp in staging and move other experimental libs here

Any opinion? Are we targetting upstream work without any DPDK staging?

Please let's make clear the status of these patches.