From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1C5D8A0A0F; Sun, 4 Jul 2021 03:53:49 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AD53340040; Sun, 4 Jul 2021 03:53:48 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id 891264003F for ; Sun, 4 Jul 2021 03:53:47 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id D3E255C007D; Sat, 3 Jul 2021 21:53:46 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sat, 03 Jul 2021 21:53:46 -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=fm1; bh= 4HbsvNwji0SLGus3PEnle6K8vkr9kblsfg7VmDzXhFc=; b=sD9ytql4x3ZK9bwS 3MVva3h9jI5IHxOrWnmOVAIosrObQ9NeVD1xvcKizyNiPYu3HbV2ddiyCkQXJiFI O47zuRk37vCuFynosZ6nC9FADv+akxKU61iBxhbAUQ+3rC84+xBNrpmszWD0Vk+F w1FxL6LXYJAu+vBl3rljRRUHf7h+TszER0MaQylVvykrSloiUqVO9NtQgRZDzd9S MKYI/Kfy5evyugvp9/C6OIkKpTuPCfXcoEu/VqS1n0C8KodFLXS8vvJcGrz2fHZx DB405G6hxyV1eeA1fSaym86x3vkrba8lNCqOVEMuqtbTjPpZkUgYBm5kOyzHGzgs YqkLVQ== 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=4HbsvNwji0SLGus3PEnle6K8vkr9kblsfg7VmDzXh Fc=; b=f7QDmuX1rZcngJYcKwgdoVpTU/Btt3+DuV7uW3eVWL4jYvv+ewi5I0UlW 76PU8F3QS+oTCXEbcek1icuX6Pm0lPK6zxHuZDgaWONHlYt0hQcNGP7qqF8TFncH hgcttCpo8m/Z/waSA3XYT4lvX8PLorUJ4BT7CzujR38DWLQHsgTb9XBr1MTIPuj+ TgRDSjzvCVyXXIbe3fGopMn/liuyMMD+C6CaJbRS9A4gXNsM9rG54Hj1mCTVBUSc ytHhg7UMIaU3dU4sDwhpNNhT136cnutTOvhjfp+yeeL7Ium3z4J7QSKqUGRI8mjE owvKcAbmAmKwBxDuyAgXu2myVjolQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeejuddggeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvffufffkjghfggfgtgesthfure dttddtvdenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpedugefgvdefudfftdefge elgffhueekgfffhfeujedtteeutdejueeiiedvffegheenucevlhhushhtvghrufhiiigv pedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrd hnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 3 Jul 2021 21:53:44 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: ferruh.yigit@intel.com, andrew.rybchenko@oktetlabs.ru, keesang.song@amd.com, anatoly.burakov@intel.com, david.marchand@redhat.com, bruce.richardson@intel.com, David Christensen , dmitry.kozliuk@gmail.com, ruifeng.wang@arm.com Date: Sun, 04 Jul 2021 03:53:43 +0200 Message-ID: <12700395.j6fn4b5UDm@thomas> In-Reply-To: <2863796.yO5TXMfXnl@thomas> References: <2863796.yO5TXMfXnl@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] NUMA node/socket X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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" 04/07/2021 03:38, Thomas Monjalon: > There are some mix between NUMA node and socket IDs in DPDK. > Examples: > * rte_eth_dev_socket_id() returns the NUMA node. > * rte_malloc use sockets to allocate the memory > > Is it critical? There is a function, implemented for Windows only, which distinguishes clearly node and socket but it assumes there is only 1 node per socket: unsigned int eal_socket_numa_node(unsigned int socket_id) { return cpu_map.sockets[socket_id].node_id; } Reminder: AMD can be configured to have multiple nodes per socket.