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 C2023A00E6 for ; Mon, 5 Aug 2019 17:13:24 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2DFD51B9C9; Mon, 5 Aug 2019 17:13:24 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id 557061B9A6 for ; Mon, 5 Aug 2019 17:13:22 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 008E42016D; Mon, 5 Aug 2019 11:13:22 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Mon, 05 Aug 2019 11:13:22 -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=eGpaPn0NCTIux1EhDKgXisU2YMM4VSD9DHzaphZZe/s=; b=YL4FSEtNrx8p 3QXamS/a5mZ7Q4o1zyO8ZcO6NW5ykTToZVHG+jlBOg/knUqKB8nD6JRsEk4bCAHb J1YU6Q7EHMuTuOdpcSLRm3CBxubgh947IbwMUgN3p/bRXthpuNuCAPNpQ59U/WCD YbujuPNS+EZbiRbx4sXJPChvfabZMn4= 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=fm3; bh=eGpaPn0NCTIux1EhDKgXisU2YMM4VSD9DHzaphZZe /s=; b=J3JCV6WClp/n0QNqPi4IX6nVDpGsP4bXnDRtCqb6Exj10m9m0Ek3yANwn P/IL5Q1cM0A5W6e/EQZUvM8LrF1aweZ4sJeX1RAdq3lVBWwXa8moXxBiQt9Z9cUl 0TWgTWvfTH7LC6aaRa0qMeFSpQ439jgcxpTA8UMcYBBh3+BazBIb7sWinzp8ci5S z8j3amD4GM8dl9fzNZZEe1gi7Czl0SReJpkxa9w8m9MGoCiXWJzK0bw503Ye51ee cH9g47wy8Zeh4veU67Pv9jwqCi/B61QXzD79P84MQAtVtiQJ5a9r/6P7j53JD/gH X5oxQAroaJltxEMlqEG8wGLAS9LQA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddruddtjedgkeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpeguphgukhdrohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtne cuvehluhhsthgvrhfuihiivgeptd 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 59B0980065; Mon, 5 Aug 2019 11:13:20 -0400 (EDT) From: Thomas Monjalon To: David Marchand Cc: dev , "Burakov, Anatoly" , Bruce Richardson , Ray Kinsella , "Traynor, Kevin" , Stephen Hemminger Date: Mon, 05 Aug 2019 17:13:19 +0200 Message-ID: <3963110.nb0tCvxbkm@xps> In-Reply-To: References: <1564752563-11850-1-git-send-email-david.marchand@redhat.com> <1667146.ajMsIp94DY@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] doc: announce malloc virt2phys symbol removal 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" 05/08/2019 17:05, David Marchand: > On Mon, Aug 5, 2019 at 4:39 PM Thomas Monjalon wrote: > > 02/08/2019 15:29, David Marchand: > > > This symbol has been deprecated for quite some time. > > > Let's drop it in the next release. > > > --- > > > --- a/doc/guides/rel_notes/deprecation.rst > > > +++ b/doc/guides/rel_notes/deprecation.rst > > > +* eal: The ``rte_malloc_virt2phy`` function has been deprecated and replaced > > > + by ``rte_malloc_virt2iova`` since v17.11 and will be removed in DPDK 19.11. > > > > For this patch and another one about removing rte_cpu_check_supported(), > > I have a general comment on the date of removal. > > > > As was stated recently in the contribution guide: > > http://git.dpdk.org/dpdk/commit/?id=7abe4a24cc > > "Deprecated APIs are removed completely just after the next LTS." > > > > The idea behind this policy is to avoid removals during LTS releases, > > in order to have at least one release before X.11 LTS for end users > > to prepare replacing the usage of the removed API. > > > > Does it make sense to postpone any API removal after 19.11? > > Those symbols have been marked as deprecated for a long time. > Users had to either disable Werror or they actually migrated to the new apis. > If they chose the lazy way of not migrating to the new apis, I suspect > they forgot about it and/or they won't look at the release notes. Yes I agree. That's why they can be surprised when hitting the removal. Avoiding this removal in LTS release is one more care for the lazy users. The question: is too much caution? > I don't particularly have a problem with waiting for 20.02, those are > easy to remove anyway.