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: Wed, 02 Mar 2016 12:21:33 +0100
Message-ID: <2396478.VfdoPKd37H@xps13>
References: <1453911849-16562-1-git-send-email-ferruh.yigit@intel.com>
 <56D6A40F.80003@redhat.com> <56D6C4BB.3070904@6wind.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: dev@dpdk.org, Avi Kivity <avi@scylladb.com>
To: Vincent JARDIN <vincent.jardin@6wind.com>,
 Stephen Hemminger <stephen@networkplumber.org>,
 Jay Rolette <rolette@infiniteio.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48])
 by dpdk.org (Postfix) with ESMTP id ED3C52C44
 for <dev@dpdk.org>; Wed,  2 Mar 2016 12:23:08 +0100 (CET)
Received: by mail-wm0-f48.google.com with SMTP id p65so75222008wmp.1
 for <dev@dpdk.org>; Wed, 02 Mar 2016 03:23:08 -0800 (PST)
In-Reply-To: <56D6C4BB.3070904@6wind.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>

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 developme=
nt
> >> 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 when i=
t
> >> gets rebuilt/reworked/scrapped.
> >>
> >
> > Exactly.
>=20
> +1 too
>=20
> We need to build on this innovation while there is a path for kernel=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 the k=
ernel?

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 dro=
pped)
and that it is a work in progress, a suggestion to discuss with the ker=
nel
community.

The kernel modules must clearly target an upstream integration.