+ Magnus & Bjorn who can give more accurate comment about kernel upstream status.
> -----Original Message----- > From: Thomas Monjalon [mailto:tho...@monjalon.net] > Sent: Tuesday, March 12, 2019 1:20 AM > To: Yigit, Ferruh <ferruh.yi...@intel.com>; Ye, Xiaolong > <xiaolong...@intel.com> > Cc: dev@dpdk.org; Zhang, Qi Z <qi.z.zh...@intel.com>; Richardson, Bruce > <bruce.richard...@intel.com> > 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 > > > ======== > > > > > > 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 > > > ============== > > > - AF_XDP is included in upstream kernel since 4.18, and AF_XDP support > > > 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=1cad078842396f0047a796694b6130fc096d97e2 > > 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? >
