From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id 66F333572 for ; Tue, 12 Mar 2019 08:55:22 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Mar 2019 00:55:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,470,1544515200"; d="scan'208";a="140043909" Received: from irsmsx105.ger.corp.intel.com ([163.33.3.28]) by FMSMGA003.fm.intel.com with ESMTP; 12 Mar 2019 00:55:20 -0700 Received: from irsmsx107.ger.corp.intel.com ([169.254.10.15]) by irsmsx105.ger.corp.intel.com ([169.254.7.210]) with mapi id 14.03.0415.000; Tue, 12 Mar 2019 07:55:02 +0000 From: "Karlsson, Magnus" To: "Zhang, Qi Z" , Thomas Monjalon , "Yigit, Ferruh" , "Ye, Xiaolong" CC: "dev@dpdk.org" , "Richardson, Bruce" , "Topel, Bjorn" Thread-Topic: [dpdk-dev] [PATCH v1 0/6] Introduce AF_XDP PMD Thread-Index: AQHU0AaXPo9mlIV7oEW/rJKVtC0sK6YGLOwAgAAKI4CAARPscIAAZMag Date: Tue, 12 Mar 2019 07:55:01 +0000 Message-ID: References: <20190301080947.91086-1-xiaolong.ye@intel.com> <7e99a95b-4df2-8dc9-806d-0f05c55363f7@intel.com> <1873176.TlTs5sP8tC@xps> <039ED4275CED7440929022BC67E706115334AEFF@SHSMSX103.ccr.corp.intel.com> In-Reply-To: <039ED4275CED7440929022BC67E706115334AEFF@SHSMSX103.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOTgzNzM0N2UtMjNhMy00Yzc5LTg0MDctMzI3YjYxNjNmYmQzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTXBMOWtVZVdMbmpZNURhS2c3bDR1RTBSYXVBaFlGV0V6UVBKVml5czUralFGanBGcHdBZlM0RjFoNVRxMUtseSJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 13 Mar 2019 11:23:31 +0100 Subject: Re: [dpdk-dev] [PATCH v1 0/6] Introduce AF_XDP PMD X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2019 07:55:23 -0000 > -----Original Message----- > From: Zhang, Qi Z > Sent: Tuesday, March 12, 2019 2:52 AM > To: Thomas Monjalon ; Yigit, Ferruh > ; Ye, Xiaolong > Cc: dev@dpdk.org; Richardson, Bruce ; > Karlsson, Magnus ; Topel, Bjorn > > Subject: RE: [dpdk-dev] [PATCH v1 0/6] Introduce AF_XDP PMD >=20 > + Magnus & Bjorn who can give more accurate comment about kernel > upstream status. >=20 >=20 > > -----Original Message----- > > From: Thomas Monjalon [mailto:thomas@monjalon.net] > > Sent: Tuesday, March 12, 2019 1:20 AM > > To: Yigit, Ferruh ; Ye, Xiaolong > > > > Cc: dev@dpdk.org; Zhang, Qi Z ; Richardson, > > Bruce > > Subject: Re: [dpdk-dev] [PATCH v1 0/6] Introduce AF_XDP PMD > > > > 11/03/2019 17:43, Ferruh Yigit: > > > On 3/1/2019 8:09 AM, Xiaolong Ye wrote: > > > > Overview > > > > =3D=3D=3D=3D=3D=3D=3D=3D > > > > > > > > This patchset adds a new PMD driver for AF_XDP which is a proposed > > > > faster version of AF_PACKET interface in Linux, see below links > > > > [1] [2] for details of AF_XDP introduction: > > > > > > > > AF_XDP roadmap > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > - AF_XDP is included in upstream kernel since 4.18, and AF_XDP supp= ort > > > > in libbpf has been merged in bpf-next/master. [3] > > > > > > And it seems it has been merged into main repo [1], I assume it will > > > be part of 5.1, which I guess will be released mid May. > > > > > > And we have release on 10 May. Taking into account that libbpf APIs > > > used extensively, does it mean we can't release af_xdp on 19.05? > > > > > > [1] > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/c > > > om > > > mit?id=3D1cad078842396f0047a796694b6130fc096d97e2 > > > > I think the requirement is to have all dependencies upstream, so we > > avoid releasing a feature not working when dependency is ready. > > > > If all is ready in Linux mainline branch, I guess we are fine, are we? Libbpf is in linux-next which means it will be in the 5.1 release. This rel= ease will likely be in the end of April if we count the normal 8 week caden= ce of releases. 8 weeks means April 28, 9 weeks =3D May 5. 10 weeks =3D May= 12. So unless we go all the way to 10 weeks, this feature should be in a s= table release before DPDK 19.05. /Magnus