From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 0EDE11B863 for ; Fri, 9 Feb 2018 12:27:45 +0100 (CET) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Feb 2018 03:27:45 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,483,1511856000"; d="scan'208";a="16866820" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.77]) by orsmga008.jf.intel.com with SMTP; 09 Feb 2018 03:27:43 -0800 Received: by (sSMTP sendmail emulation); Fri, 09 Feb 2018 11:27:42 +0000 Date: Fri, 9 Feb 2018 11:27:41 +0000 From: Bruce Richardson To: Victor Huertas Cc: users@dpdk.org Message-ID: <20180209112740.GA4756@bricha3-MOBL3.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.9.1 (2017-09-22) Subject: Re: [dpdk-users] [dpdk-dev] Nehalem Intel Xeon X5506 architecture and PCIe NIC association to Numa node X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Feb 2018 11:27:46 -0000 Moving to users list, since that is more relevant than dev. On Thu, Feb 08, 2018 at 07:36:30PM +0100, Victor Huertas wrote: > Bruce, > > > My requirements are not that much (500 Mbps and 1 Gbps desirable). > > > Thanks for your references links I will have a look at them. > > > Regarding the NIC detection in the DPDK app by the DPDK EAL initialization > after successfully having loaded the vfio-pci, it happens something strange. > > The nb_ports = rte_eth_dev_count(); is always returning 0. > > > Therefore it shows an error telling that "port 0 is not present on the > board". > > > The EAL seems to detect the VFIOs as the only two logs that shows when > initializing regarding VFIO are: > > > EAL: Probing VFIO support... > > EAL: VFIO support initialized > > > And nothing else... shouldn't the EAL detect the two NICs I associated to > the VFIO? very strange... > > Yes, it should. Can you please send full output on startup. Also, can you try using igb_uio module instead of vfio and see if that works for you. Regards, /Bruce > Regards, > > > PD: I have changed the email address account in order to avoid sending > these disturbing disclaimers. Sorry. > > > -----Mensaje original----- > De: Bruce Richardson [mailto:bruce.richardson@intel.com] > Enviado el: jueves, 08 de febrero de 2018 17:42 > Para: Huertas García, Víctor > CC: dev@dpdk.org > Asunto: Re: [dpdk-dev] Nehalem Intel Xeon X5506 architecture and PCIe NIC > association to Numa node > > > > On Thu, Feb 08, 2018 at 04:27:36PM +0000, Huertas García, Víctor wrote: > > > > > > Hi all, > > > > > > After having tried many ways to make the PCIe NIC card appear associated > to a numa node, I haven't been able to do it. > > > That is, every time I try to look at which numa node belongs it always > returns -1. > > > > > > $ cat /sys/bus/pci/devices/0000\:04\:00.1/numa_node > > > -1 > > > > > > $ cat /sys/bus/pci/devices/0000\:04\:00.0/numa_node > > > -1 > > > > > > Using lstopo, I confirm that all PCI cards are "outside" of any Numa > node. > > > > > > I have read in previous posted messages in dpdk-dev community that this > is normal in Nehalem generation Xeon architecture and there is nothing I > can do about it. Can somebody confirm this? > > > > For that generation architecture, it is indeed expected. The NICs are not > directly connected to any NUMA node. > > > > > If so, what implications could this have on packet capture and > performance? > > > > Unsurprisingly, it's the case that newer platforms will perform better, as > you are missing out on performance benefits from improved cores and also > features like Intel® DDIO [1]. > > However, what I/O throughput are you hoping to get from your system? > > Depending on your requirements, what you have may be enough. Some people > use DPDK on lower-end platforms because that is all that they need. You may > also find the chart on slide 6 of [2] of use to see how the max throughput > of a platform has improved over time (and has improved further since that > chart was published). > > > > > > > > Are the NICs available in my DPDK applications? Do I have to specifically > "add" them by "-w 04:00.1 - w 04:00.0"? > > > > Yes, your NICs will still be available, even without NUMA affinity, and no, > you should not need to explicitly whitelist them - though you can if you > want. So long as they are bound to a uio or vfio driver (e.g. > > igb_uio or vfio-pci), they should be detected by DPDK EAL init and made > available to your app. > > > > > Is RSS supported and usable from the DPDK application? > > > > Yes, at least for Intel NICs, and probably most other DPDK-supported NICs > too. > > > > > > > > Thanks a lot for your attention > > > > > > Victor > > > > > > > /Bruce > > > > [1] https://www.intel.com/content/www/us/en/io/data-direct-i-o-t > echnology.html > > [2] https://dpdksummit.com/Archive/pdf/2016Germany/DPDK-2016- > DPDK_FD_IO_Introduction.pdf > > > > PS: This is a public list, so email disclaimers are rather pointless. > > It's best if they can be removed from mails sent here. > > > > > -- > Victor