From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 ; Thu, 10 Mar 2016 01:06:36 +0100 (CET) Received: by mail-wm0-f53.google.com with SMTP id p65so7410882wmp.0 for ; Wed, 09 Mar 2016 16:06:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:organization:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=u5GBo9Tw5gu9tlM5WXUSEJwg8dJLZahEURcEXJzuSBI=; b=tq76WOsSvmS4rgCSTVdssTFeuCCMJajWyez6vt/iEazUQxZ3lmloWP3T48H6qkHKFN XOnFIC6UWfUvF7xRH8sOLUjYp9zqJL5GJjpG4geIKlxcgiMxnDLwpt3ISpAprxctDX7h uRBae0vMR4uN+tum8W45nQelAjTx/j+ZRTCJpxUpcW21VX4efclQqDrZUzWsc5yDUMPN daGeZ1/e1gsXEbMn9+aHsGV1vOt7wtPUvDmQRtGsdyvBDqu1O5pZQKRCd22B1CyvWj+J 8L4C4/7zC1yzPeAZXgOlc0WiXOQ7tOH+b1nu2ZISIlOzq61l/oGPLGO6TcIb8ORQxPKX KEgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding; bh=u5GBo9Tw5gu9tlM5WXUSEJwg8dJLZahEURcEXJzuSBI=; b=ZYmIR+E0CLbBbSXSwTRhj/5OK4tJCXJkTtqcLh8/SnEex8jMIwlDpEd+BgV+4Ct6qZ EJKDxaVonUjNv8E5wahh7xrqIby30Yj1ycJLEX37DwHhOfLpub43JTuqr49XZnWafQuN mHcE4K1Y3qABAbeYkFGwGZ0y/ihZUbYC+5B/I61qmD8OeTAIUAJydEBIVM63aZ2ZSw8J fjV6khwCEX7uuMN/zlej7ykNSQBynHOwrmvOvJNPE/HgavmyKIEDR3kYwYdzROcQ2nU/ LhdOtngQTK1TFVMUKWsmD5iF98ez+5e1XUHm2Zd+fkmReW+GwkJIurYf+fULbRCKXh83 oi6w== X-Gm-Message-State: AD7BkJIkPN3LDBTUxoI8k9VcwuSrjbbn31MX+qEY2Ti88P0u9RD3bRztsPbUG1XSQIyDZ3ab X-Received: by 10.28.176.200 with SMTP id z191mr389105wme.91.1457568395887; Wed, 09 Mar 2016 16:06:35 -0800 (PST) Received: from xps13.localnet (91.111.75.86.rev.sfr.net. [86.75.111.91]) by smtp.gmail.com with ESMTPSA id lh1sm869629wjb.20.2016.03.09.16.06.27 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Mar 2016 16:06:28 -0800 (PST) From: Thomas Monjalon To: ferruh.yigit@intel.com Date: Thu, 10 Mar 2016 01:04:48 +0100 Message-ID: <4528438.gG6caYbQZH@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <5360490.85HbqvIh1a@xps13> References: <1453911849-16562-1-git-send-email-ferruh.yigit@intel.com> <2396478.VfdoPKd37H@xps13> <5360490.85HbqvIh1a@xps13> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Cc: Avi Kivity , dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH 1/3] kcp: add kernel control path kernel module X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Mar 2016 00:06:36 -0000 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.