From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 832691B80A for ; Thu, 8 Feb 2018 17:42:32 +0100 (CET) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Feb 2018 08:42:29 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,479,1511856000"; d="scan'208";a="33167171" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.77]) by orsmga002.jf.intel.com with SMTP; 08 Feb 2018 08:42:27 -0800 Received: by (sSMTP sendmail emulation); Thu, 08 Feb 2018 16:42:26 +0000 Date: Thu, 8 Feb 2018 16:42:24 +0000 From: Bruce Richardson To: Huertas =?iso-8859-1?Q?Garc=EDa=2C_V=EDctor?= Cc: "dev@dpdk.org" Message-ID: <20180208164224.GA4772@bricha3-MOBL3.ger.corp.intel.com> References: <9d72fe002dcf4740969a652bf7df057f@MadMail01.indra.es> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9d72fe002dcf4740969a652bf7df057f@MadMail01.indra.es> Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.9.1 (2017-09-22) Subject: Re: [dpdk-dev] Nehalem Intel Xeon X5506 architecture and PCIe NIC association to Numa node X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Feb 2018 16:42:34 -0000 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-technology.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. > ________________________________ > > Este correo electrónico y, en su caso, cualquier fichero anexo al mismo, contiene información de carácter confidencial exclusivamente dirigida a su destinatario o destinatarios. Si no es vd. el destinatario indicado, queda notificado que la lectura, utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. En el caso de haber recibido este correo electrónico por error, se ruega notificar inmediatamente esta circunstancia mediante reenvío a la dirección electrónica del remitente. > Evite imprimir este mensaje si no es estrictamente necesario. > > This email and any file attached to it (when applicable) contain(s) confidential information that is exclusively addressed to its recipient(s). If you are not the indicated recipient, you are informed that reading, using, disseminating and/or copying it without authorisation is forbidden in accordance with the legislation in effect. If you have received this email by mistake, please immediately notify the sender of the situation by resending it to their email address. > Avoid printing this message if it is not absolutely necessary.