From mboxrd@z Thu Jan  1 00:00:00 1970
From: Vincent JARDIN <vincent.jardin@6wind.com>
Subject: Re: [PATCH 1/3] kcp: add kernel control path kernel
	module
Date: Wed, 2 Mar 2016 11:47:23 +0100
Message-ID: <56D6C4BB.3070904@6wind.com>
References: <1453911849-16562-1-git-send-email-ferruh.yigit@intel.com>
 <56D420E5.9010802@intel.com> <56D42462.3020905@scylladb.com>
 <1945473.Tiatd2m80T@xps13>
 <CADNuJVof3FmLHsJG2MkViLpF0dr28PB6NZdVC7=vB+ZExHfO3w@mail.gmail.com>
 <20160301180255.3ef1a17e@xeon-e3> <56D6A40F.80003@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: DPDK <dev@dpdk.org>, Avi Kivity <avi@scylladb.com>
To: Panu Matilainen <pmatilai@redhat.com>,
 Stephen Hemminger <stephen@networkplumber.org>,
 Jay Rolette <rolette@infiniteio.com>,
 "thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42])
 by dpdk.org (Postfix) with ESMTP id 60E212BE5
 for <dev@dpdk.org>; Wed,  2 Mar 2016 11:47:43 +0100 (CET)
Received: by mail-wm0-f42.google.com with SMTP id l68so74094132wml.0
 for <dev@dpdk.org>; Wed, 02 Mar 2016 02:47:43 -0800 (PST)
In-Reply-To: <56D6A40F.80003@redhat.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>

Le 02/03/2016 09:27, Panu Matilainen a =C3=A9crit :
>>> I'd like to see these be merged.
>>>
>>> Jay
>>
>> The code is really not ready. I am okay with cooperative development
>> 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 it
>> gets rebuilt/reworked/scrapped.
>>
>
> Exactly.

+1 too

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.

Thomas,

can we open a staging folder into the DPDK like it is done into the kerne=
l?

Thank you,
   Vincent