From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41]) by dpdk.org (Postfix) with ESMTP id 8C9631B739 for ; Thu, 8 Feb 2018 19:36:31 +0100 (CET) Received: by mail-wm0-f41.google.com with SMTP id t74so11273936wme.3 for ; Thu, 08 Feb 2018 10:36:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=NuEYJnTYIqpXE8jN9SwEudXnYqP9uukjrE73mmaXljc=; b=XbuwOqN0PCH7ta+4uaskiQOA97nYNibSlaGW3qbir4++5hYtTAPRqfhLycleOYoSwO DyDoI85GP+71pjj8+Gvyn1Me/9YPMA30/dKznID8ufu687mmoDhV20HlKRFI8SN0t9iS E4+cmJEaFGGE5MAZV8v2e83Z/U+CqR8QM9YoB0geUupyy+FuOeDDIEvJNVoJiaQGWSgJ ssy52VQI4ZG5j7tZwZvdMQCUHf05bQymjIONHOxtyel6IQQSVyOiJk2Brmn3qZKlI/ES 1p6Aa5mWH/Qsd+yuwqUqeigjQSglKL+vS2DIUfCXY2NjRFof21M6Q0FtSZHzUx3ywm7z QsuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=NuEYJnTYIqpXE8jN9SwEudXnYqP9uukjrE73mmaXljc=; b=SNNmnRwmwxyP5tMqbgOlPrgLAjZQAY2OpSfKbEpgnhs4ksOuJ1Oj7DKGJNGugsS+eY UZemYNwAR5QmVm87CFW5CCmJUGpKfuCCrtdYCeEHnEakvf9eD7SVJIqGIIQTs0qVgkKl 9P2MfIUyjfKCAtHAxmkmPB5EJLn2g2Mz3gWevz36MSoEcrp4wLtFL76F5IDZ8N78xvzi 3mcSdK/jJrDnocLXj+StbCS5dEo1g90Xe+DouyWslgZm68n3l5/1mv+pNHoFu8XV95rU K6VdQ/j2f1RIhBFyog74g9VBSLoPyAfnT2B6Yfg3SDZw5MLOieh9F14dnZpG6r/6TWu1 7z2A== X-Gm-Message-State: APf1xPAayzEG0vOUBP3mKyLLCmxt/BNKJ9q4c0cNDtWjq2FODpleCBJa NrZpQ/OyA1hcsL0GW4lZFGGkFD27xngkHtJ7HWg= X-Google-Smtp-Source: AH8x227+ImjdhXXIAKMAtEd07dtMmQyl03D2mUZUIj1NJTXwUEr/XEQKCOwnt5jJA2AhhGXmO6VinJMFtiNVLvBUsHQ= X-Received: by 10.80.173.202 with SMTP id b10mr138603edd.209.1518114991213; Thu, 08 Feb 2018 10:36:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.185.37 with HTTP; Thu, 8 Feb 2018 10:36:30 -0800 (PST) From: Victor Huertas Date: Thu, 8 Feb 2018 19:36:30 +0100 Message-ID: To: bruce.richardson@intel.com Cc: dev@dpdk.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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 18:36:31 -0000 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 =3D 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... 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=C3=ADa, V=C3=ADctor 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=C3=ADa, V=C3=ADctor = 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=C2=AE 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. --=20 Victor