From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 1342F2C24 for <dev@dpdk.org>; Mon, 11 Mar 2019 18:27:00 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6A3B82A34C; Mon, 11 Mar 2019 13:26:59 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 11 Mar 2019 13:26:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=N4mf7ffbOtEB8GWUMJBCY+CbYkLDimd/GGoZG6gK7mQ=; b=EUzsAiRef6HG NliWYxjjNM8tFB+FcewG+CZCXciR8Kn/HZGsqn24eUUWNlyOdmQoT+0wFvUrdOkQ O5VkiRa63VUvDQ7++O4jlBc5GYUpUmpFQ+xwY/yB3ax4ZHKGLZ9BRli+6jkoICIp BqfOSg0C6X9+WMgQa+xuLgsyqpDLjSc= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=N4mf7ffbOtEB8GWUMJBCY+CbYkLDimd/GGoZG6gK7 mQ=; b=1tU5NqM+RNvVIaXfm2InVw4PjCKKhnRvnJoErAXxIJz9T9oNcZWSuYRbm PQ1HEp5kkrCljsF0iBaLcWMuBlzitRvih7Sr192c+lrscQEOQJWOmO6hB2HOBt/H KLHYNBct2haSjb53Lfbk9RNnFq7N8kx6knUk4WX5hKU4RA+QVTAXzUdl+OLb5PWQ y5L+5Do46kRgwGwttHM3C2uk1w+IE2KN1zgjCirnt3eHNjvcuVIGI7i8fKtI0b0q ZBmF9Y3aNzgc4mjddqi4wY0IB97XPT61+TR7L0Qzw3SrWwHzx4NNFqkMeMLgJbgl vGmTymR+LCh6MqxW4d2ADEDJ829BA== X-ME-Sender: <xms:YpqGXBsFi3kB7xzJGezKXvICHAbw_OSlOX8YDt2HsVEr3ILGnBIIuw> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrgeeigddutdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpehkvghrnhgvlhdrohhrghenucfkphepjeejrddufeeirdduleejrdeiuden ucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth enucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: <xmx:YpqGXIueH50mKx_cI3TqKIjsQocbkKif1gpJ5cITOSJEMpo11hhHPQ> <xmx:YpqGXN5a1J9X9BiRUi7_ubfjoOv0EoCODeSVh_hEPapR-Gepa0isog> <xmx:YpqGXJZOS63eSDLBt8GVBMyqUfDlVR1DwEw36XMNrJtQ9Mso3yMnQQ> <xmx:Y5qGXP8q4UJUuCetm2lZzQoYVSmqY-fX45WW3p-g_Esi04OFR_GyIg> Received: from xps.localnet (61.197.136.77.rev.sfr.net [77.136.197.61]) by mail.messagingengine.com (Postfix) with ESMTPA id EDDB8100E5; Mon, 11 Mar 2019 13:26:56 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: Ferruh Yigit <ferruh.yigit@intel.com>, Xiaolong Ye <xiaolong.ye@intel.com> Cc: dev@dpdk.org, Qi Zhang <qi.z.zhang@intel.com>, Bruce Richardson <bruce.richardson@intel.com> Date: Mon, 11 Mar 2019 18:19:41 +0100 Message-ID: <1873176.TlTs5sP8tC@xps> In-Reply-To: <7e99a95b-4df2-8dc9-806d-0f05c55363f7@intel.com> References: <20190301080947.91086-1-xiaolong.ye@intel.com> <7e99a95b-4df2-8dc9-806d-0f05c55363f7@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Mon, 11 Mar 2019 17:27:00 -0000 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/commit?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?