From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 72C5549E0 for ; Tue, 12 Mar 2019 02:52:47 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Mar 2019 18:52:46 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,468,1544515200"; d="scan'208";a="326421175" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga006.fm.intel.com with ESMTP; 11 Mar 2019 18:52:45 -0700 Received: from fmsmsx157.amr.corp.intel.com (10.18.116.73) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 11 Mar 2019 18:52:45 -0700 Received: from shsmsx108.ccr.corp.intel.com (10.239.4.97) by FMSMSX157.amr.corp.intel.com (10.18.116.73) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 11 Mar 2019 18:52:45 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.134]) by SHSMSX108.ccr.corp.intel.com ([169.254.8.57]) with mapi id 14.03.0415.000; Tue, 12 Mar 2019 09:51:58 +0800 From: "Zhang, Qi Z" To: Thomas Monjalon , "Yigit, Ferruh" , "Ye, Xiaolong" CC: "dev@dpdk.org" , "Richardson, Bruce" , "Karlsson, Magnus" , "Topel, Bjorn" Thread-Topic: [dpdk-dev] [PATCH v1 0/6] Introduce AF_XDP PMD Thread-Index: AQHU0AaXPo9mlIV7oEW/rJKVtC0sK6YGLOwAgAAKI4CAARPscA== Date: Tue, 12 Mar 2019 01:51:57 +0000 Message-ID: <039ED4275CED7440929022BC67E706115334AEFF@SHSMSX103.ccr.corp.intel.com> References: <20190301080947.91086-1-xiaolong.ye@intel.com> <7e99a95b-4df2-8dc9-806d-0f05c55363f7@intel.com> <1873176.TlTs5sP8tC@xps> In-Reply-To: <1873176.TlTs5sP8tC@xps> 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: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 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 01:52:48 -0000 + Magnus & Bjorn who can give more accurate comment about kernel upstream s= tatus. > -----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 >=20 > 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 suppor= t > > > 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/com > > mit?id=3D1cad078842396f0047a796694b6130fc096d97e2 >=20 > I think the requirement is to have all dependencies upstream, so we avoid > releasing a feature not working when dependency is ready. >=20 > If all is ready in Linux mainline branch, I guess we are fine, are we? >=20