From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] memzone: Check socket_id value when creating memzone. Date: Mon, 05 Jun 2017 18:24:20 +0200 Message-ID: <2684435.WV1LPMSqPV@xps> References: <1494569023-7564-1-git-send-email-nic@opencloud.tech> <20170512084220.GB53020@bricha3-MOBL3.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Bruce Richardson To: Tonghao Zhang Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id EDF897CB6 for ; Mon, 5 Jun 2017 18:24:21 +0200 (CEST) In-Reply-To: <20170512084220.GB53020@bricha3-MOBL3.ger.corp.intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 12/05/2017 10:42, Bruce Richardson: > On Thu, May 11, 2017 at 11:03:43PM -0700, Tonghao Zhang wrote: > > If the socket_id is invalid (e.g. -2, -3), the > > memzone_reserve_aligned_thread_unsafe should return the > > EINVAL and not ENOMEM. To avoid it, we should check the > > socket_id before calling malloc_heap_alloc. > > > > Signed-off-by: Tonghao Zhang > > Looks a sensible thing to do. > > Acked-by: Bruce Richardson Applied, thanks