dpif-netdev: report numa node number on pmd thread create failure
authorPanu Matilainen <pmatilai@redhat.com>
Wed, 6 Apr 2016 12:52:30 +0000 (15:52 +0300)
committerDaniele Di Proietto <diproiettod@vmware.com>
Wed, 6 Apr 2016 18:38:32 +0000 (11:38 -0700)
commit27955e9852ec3a58789195b1fe7b00355f2f16df
tree288151e0d78ce6bcc8e3f41af4e207b786791fb8
parent7d433ae57ebb90cd68e8fa948a096f619ac4e2d8
dpif-netdev: report numa node number on pmd thread create failure

Since PMD threads are placed on the NUMA node of the port regardless
of a possible pmd-cpu-mask setting, this can lead to a somewhat
confusing "out of unpinned cores" message - there might be plenty
of available cores in the mask but they cannot be used if the port
is on different NUMA node than the cores. Report the NUMA node
number to help diagnosing the issue.

Reported-at: https://bugzilla.redhat.com/show_bug.cgi?id=1295952
Signed-off-by: Panu Matilainen <pmatilai@redhat.com>
Acked-by: Daniele Di Proietto <diproiettod@vmware.com>
lib/dpif-netdev.c