From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1FC70A00BE; Tue, 29 Oct 2019 19:31:04 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4F4381BF4F; Tue, 29 Oct 2019 19:31:03 +0100 (CET) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 695901BEC0 for ; Tue, 29 Oct 2019 19:31:02 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id C919A21FE8; Tue, 29 Oct 2019 14:30:59 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 29 Oct 2019 14:30: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=ExaWAFngevb/jqlJtQVHG8HAtJi3RBtFod62R15Shzg=; b=oUaJBmDQIWKP msAGhWfzd6OipCd/BecNQeivEYhsdGtGxCOpgYdUnB159JQyFuHciV1WIqIh1sxr vTzUpzSW2T1MbvmN/ATmxRsi7MzC4hwkiKRb7WNwK/+mzbccqf+hMVzBrsgQKAO5 IyHNS6GC/kFHS1H4BBfRQGY+cnRekN0= 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=fm1; bh=ExaWAFngevb/jqlJtQVHG8HAtJi3RBtFod62R15Sh zg=; b=TKDhfOiuty3LVnynfcoVCK+iQIlvlyN+gcSIDlGO+WFMNwofgnpyynkhR 4TpjHSrC0V1W9ij7sno2yzO777H3DYAAdhgjZm+VlzSDKbdoQkIfau7r/skv3xmU DiYEFTyunmE/+pQJXXGpa1UqvD0PXBWq9EV6fuwSFzIhqxTXgTNgdhCIBfGqbeET RaHJaOe+yzdjRO6GDfV9AkoOTUbJowGrQ6ec+b4HQkk1AzOo4jv81dX34ygVps62 V0ZummJ8ZIy8wXkACvcLMygb8PtPiUNpjby7Rg6kXVVaaORdcyQIZCkylUTzeMRv h/GRK8csJPCa//3ecXnY35DSu/XQw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddtuddgudduvdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc fkphepjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpeht hhhomhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id D0CD980061; Tue, 29 Oct 2019 14:30:57 -0400 (EDT) From: Thomas Monjalon To: Slava Ovsiienko Cc: Andrew Rybchenko , "dev@dpdk.org" , Matan Azrad , "olivier.matz@6wind.com" , Ori Kam Date: Tue, 29 Oct 2019 19:30:27 +0100 Message-ID: <5596453.zqmvSB3bmi@xps> In-Reply-To: References: <1571922495-4588-1-git-send-email-viacheslavo@mellanox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v4] ethdev: extend flow metadata 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 29/10/2019 18:19, Slava Ovsiienko: > From: Andrew Rybchenko > > > --- a/doc/guides/rel_notes/deprecation.rst > > > +++ b/doc/guides/rel_notes/deprecation.rst > > > +* ethdev: DEV_TX_OFFLOAD_MATCH_METADATA will be removed, static > > > +metadata > > > + mbuf field will be removed in 20.02, metadata feature will use > > > +dynamic mbuf > > > + field and flag instead. > > > + > > > > Isn't it breaking stable API/ABI? Should target release be 20.11? > > tx_metadata is in union, it should not be ABI break. > And we propose to remove tx_metadata at all in 19.11 > and share the dynamic metadata field between Rx and Tx METAdata. Yes please, let's remove tx_metadata from mbuf now, while adding metadata dynamic field. I am sure nobody will complain that we sanitized this feature before releasing DPDK 19.11 LTS.