> Thanks for the patch!
> I'm not sure how to best handle the libnuma dependency. Question:
> Is it still useful to move the device to a PMD thread on the appropriate
> numa socket, even if DPDK is compiled without
> CONFIG_RTE_LIBRTE_VHOST_NUMA? If it's useful, I'm fine with the
> approach followe
Thanks for the patch!
I'm not sure how to best handle the libnuma dependency. Question:
Is it still useful to move the device to a PMD thread on the appropriate
numa socket, even if DPDK is compiled without
CONFIG_RTE_LIBRTE_VHOST_NUMA? If it's useful, I'm fine with the
approach followed by this p
> >
> >This commit allows for vHost User memory from QEMU, DPDK and OVS, as
> >well as the servicing PMD, to all come from the same socket.
> >
> >The socket id of a vhost-user port used to be set to that of the master
> >lcore.
> >Now it is possible to update the socket id if it is detected (duri
>-Original Message-
>From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Ciara Loftus
>Sent: Tuesday, May 24, 2016 2:15 PM
>To: dev@openvswitch.org
>Subject: [ovs-dev] [PATCH] netdev-dpdk: NUMA Aware vHost User
>
>This commit allows for vHost User memory from Q
This commit allows for vHost User memory from QEMU, DPDK and OVS, as
well as the servicing PMD, to all come from the same socket.
The socket id of a vhost-user port used to be set to that of the master
lcore. Now it is possible to update the socket id if it is detected
(during VM boot) that the vh
