>
> Thanks for the patch, I'll put this in the use case list for
> my series if I need to resend it!
>
> It would be nice to get the numa socket information without
> linking OVS with libnuma, maybe using some DPDK api. From
> a quick look I didn't find any way, but maybe you know a
> better way.
On Thu, Mar 10, 2016 at 11:24:36PM +, Daniele Di Proietto wrote:
> ovs-numa reads the CPUs and NUMA nodes configuration from sysfs.
> It is only used to decide how to set the affinity of pmd threads.
>
> This new code just needs get_mempolicy() from libnuma: it is used
> to get the NUMA node o
ovs-numa reads the CPUs and NUMA nodes configuration from sysfs.
It is only used to decide how to set the affinity of pmd threads.
This new code just needs get_mempolicy() from libnuma: it is used
to get the NUMA node of a virtual address and it is simply a wrapper
to a system call. Want do you t
How does this numa library relate to lib/ovs-numa.[ch]?
On Thu, Mar 10, 2016 at 01:22:42AM +, Daniele Di Proietto wrote:
> Thanks for the patch, I'll put this in the use case list for
> my series if I need to resend it!
>
> It would be nice to get the numa socket information without
> linking
Thanks for the patch, I'll put this in the use case list for
my series if I need to resend it!
It would be nice to get the numa socket information without
linking OVS with libnuma, maybe using some DPDK api. From
a quick look I didn't find any way, but maybe you know a
better way.
Some preliminar
