From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 047691D8A for ; Wed, 22 Nov 2017 09:54:20 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 71B502094B; Wed, 22 Nov 2017 03:54:20 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 22 Nov 2017 03:54:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=DvlwKP0uM/BNiT13eC3VttwhU4 bhh/4M1U3H0om2oOE=; b=AcuSbwxgJ59RAUeewe7DvHRwGibiq37/gCPBGib8OZ I6neEvlmVYY6JLdHcn1VYIiXWMTHAA+RWuDZNGD0+LjyDlDyvxOlBn+IQIbr1814 9niFJyniMjpXSEZmvH2aSisz89AsRs26w5MSPZgiHDE8FJkT1vPAfCMja4GoljUe E= 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-sender:x-me-sender:x-sasl-enc; s=fm1; bh=DvlwKP 0uM/BNiT13eC3VttwhU4bhh/4M1U3H0om2oOE=; b=qHf2AWm8718fEMHL5zE8EB 9Q6i0zOP4xBlq8/TCo9RIVdxjrN+/LA/j3vXeUlKCLe4abAp/edTYrwj2GUpvUD8 WS6SzdRAfVTSwa/1q74l1GcN2z5M6Y88cZ+VtyrOVI/HsqcDNkuZWJlh//O7BgOJ i3XOEJ5UR39idYw41+HY7g8K+P3ZE0acSV28w6QZESD7kf3gCFE2FieJbhjBmouj S2c9RbAmD73dACT/fsKN0B+QhW+KEgBmGVk3OEtl9JrQ4I44CWUrgfDidBdRP9E6 DOjLpanFM+kC3P13N0LeL4jyfq9JA1yMmci8cy+mHNHBsHmEkpDlrsNjnsLCGRWw == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 23101244E7; Wed, 22 Nov 2017 03:54:20 -0500 (EST) From: Thomas Monjalon To: Shahaf Shuler , Ferruh Yigit Cc: John McNamara , dev@dpdk.org Date: Wed, 22 Nov 2017 09:54:19 +0100 Message-ID: <7543023.ylcdRrKDlW@xps> In-Reply-To: References: <20171121014241.61050-1-ferruh.yigit@intel.com> <1af4e9dc-35af-f4c1-f750-297c6835b19c@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH 5/6] doc: add offload flag to PMD todo list 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: Wed, 22 Nov 2017 08:54:21 -0000 22/11/2017 09:43, Shahaf Shuler: > Tuesday, November 21, 2017 8:03 PM, Ferruh Yigit: > > On 11/21/2017 12:32 AM, Shahaf Shuler wrote: > > > > > > The deprecation of the old offloads API is set to 18.05 [1]. my > > understanding was that we agreed to convert all PMDs on 18.02. > > > If the PMD deadline is going to be postponed I think the ethdev > > deprecation should be updated. > > > > Hi Shahaf, > > > > I put deadlines roughly and they need to be discussed here. > > > > But 18.02 deadline is not far away. > > I think it is not realistic to expect all relevant PMDs do this conversion on > > time, what do you think? > > I cannot tell about other vendors plans. For mlx4 and mlx5 I plan to convert on 18.02. > From the discussion we had on 17.11 for this feature we agreed to split it into 2, and the PMD part will be on 18.02. no one objected. > > Maybe on the next Tech-board you can have a sync between some of the vendors to see the plans. > If not all can make it, we should postpone the deprecation of the old API. The current plan looks good to me. We try to migrate to the new API in 18.02. If some drivers are not migrated in 18.02, we urge them to do so in 18.05. And we remove the old API in 18.05.