From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [Q] l2fwd in examples directory Date: Fri, 16 Oct 2015 14:43:21 +0100 Message-ID: <20151016134320.GE9980@bricha3-MOBL3> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: Moon-Sang Lee Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 7674E9E7 for ; Fri, 16 Oct 2015 15:43:37 +0200 (CEST) Content-Disposition: inline In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, Oct 15, 2015 at 11:08:57AM +0900, Moon-Sang Lee wrote: > There is codes as below in examples/l2fwd/main.c and I think > rte_eth_dev_socket_id(portid) > always returns -1(SOCKET_ID_ANY) since there is no association code between > port and > lcore in the example codes. Can you perhaps clarify what you mean here. On modern NUMA systems, such as those from Intel :-), the PCI slots are directly connected to the CPU sockets, so the ethernet ports do indeed have a direct NUMA affinity. It's not something that the app needs to specify. /Bruce > (i.e. I need to find a matching lcore from > lcore_queue_conf[] with portid > and call rte_lcore_to_socket_id(lcore_id).) > > /* init one RX queue */ > fflush(stdout); > ret = rte_eth_rx_queue_setup(portid, 0, nb_rxd, > rte_eth_dev_socket_id(portid), > NULL, > l2fwd_pktmbuf_pool); > if (ret < 0) > rte_exit(EXIT_FAILURE, "rte_eth_rx_queue_setup:err=%d, > port=%u\n", > ret, (unsigned) portid); > > It works fine even though memory is allocated in different NUMA node. But I > wonder there is > a DPDK API that associates inlcore to port internally thus > rte_eth_devices[portid].pci_dev->numa_node > contains proper node. > > > -- > Moon-Sang Lee, SW Engineer > Email: sang0627@gmail.com > Wisdom begins in wonder. *Socrates*