From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 80E62A05D3 for ; Wed, 27 Mar 2019 12:03:36 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 606095681; Wed, 27 Mar 2019 12:03:36 +0100 (CET) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 04C255681; Wed, 27 Mar 2019 12:03:34 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 72983220F4; Wed, 27 Mar 2019 07:03:34 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 27 Mar 2019 07:03:34 -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=vFOvZUXBYDNSYnFHXTbUvzy1u1Ev+VDMG351mT/BHpU=; b=OrAaommYTjQU nrxCmE1qnunzv3J4olxfPn4IyQq1i5CynI5/WOCkqjyWzZ2+bRbzO10rVP3YVNFD aH92dquuplEqC+a2xHYMO3AlqrjLx7JzoDmrM0Oge7TnUXdvwNMsjHuvsdd6e/BE yZjs7rm2C7IiqZ5232jB7hOT5FTz68M= 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=vFOvZUXBYDNSYnFHXTbUvzy1u1Ev+VDMG351mT/BH pU=; b=KKcaF8N4or201UdTZhQaxdk/3Ff5ey7cuD0fFRLIwoMhIyr/2l5R9V4Yn /FoGxHfeKM5T1tMvrVn4+KSJGFyGEFhAfmW/V1HYB/0YYKvoOOwDx3aNo3v8G3VM y+++DHPbhW6ShOGees+eAp2REIJfhG38+kvbXNonRw2sWST8zunzNbtzoEK6da+K IzQK1ZZm9QN6ORRhnWc+nKtEXZGwwvoFzwjHJmhDPqfepMLEgoN6cpnGRuMpuMaR OWVf9HQGigbr+Zfmn+9UgdD5lLJNdcrzsDefd8RwrobVb4nMEgblXGPo5RPlSq57 tOu0JM/lMQ00VWAei6zCjf4IAFo8Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkedvgddvtdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd 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 0E01510317; Wed, 27 Mar 2019 07:03:32 -0400 (EDT) From: Thomas Monjalon To: Anatoly Burakov Cc: stable@dpdk.org, dev@dpdk.org Date: Wed, 27 Mar 2019 12:03:30 +0100 Message-ID: <2037565.XbdSNCcqL8@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-stable] [PATCH] malloc: fix documentation for realloc X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" 22/02/2019 16:29, Anatoly Burakov: > The documentation for rte_realloc claims that the resized area > will always reside on the same NUMA node. This is not actually > the case - while *resized* area will be on the same NUMA node, > if resizing the area is not possible, then the memory will be > reallocated using rte_malloc(), which can allocate memory on > another NUMA node, depending on which lcore rte_realloc() was > called from and which NUMA nodes have memory available. > > Fix the API doc to match the actual code of rte_realloc(). > > Fixes: af75078fece3 ("first public release") > Cc: stable@dpdk.org > > Signed-off-by: Anatoly Burakov Applied, thanks