[dpdk-dev] Nehalem Intel Xeon X5506 architecture and PCIe NIC association to Numa node

[Huertas García, Víctor]

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?
If so, what implications could this have on packet capture and performance?

Are the NICs available in my DPDK applications? Do I have to specifically "add" them by "-w 04:00.1 - w 04:00.0"?
Is RSS supported and usable from the DPDK application?

Thanks a lot for your attention

Victor

________________________________

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.