netdev-dpdk: Restore thread affinity after DPDK init
authorAaron Conole <aconole@redhat.com>
Fri, 29 Apr 2016 17:44:00 +0000 (13:44 -0400)
committerDaniele Di Proietto <diproiettod@vmware.com>
Fri, 29 Apr 2016 22:07:39 +0000 (15:07 -0700)
commit563c98d86e77ba0345661e212137906747958db1
treef1bc84f7e029a8b89db60247e6643864b6ebd0be
parentace39a6f63d4c28344ca0e2a2c4233ddbc16b07c
netdev-dpdk: Restore thread affinity after DPDK init

When the DPDK init function is called, it changes the executing thread's
CPU affinity to a single core specified in -c. This will result in the
userspace bridge configuration thread being rebound, even if that is not
the intent.

This change fixes that behavior by rebinding to the original thread
affinity after calling dpdk_init().

Co-authored-by: Kevin Traynor <kevin.traynor@intel.com>
Signed-off-by: Kevin Traynor <kevin.traynor@intel.com>
Signed-off-by: Aaron Conole <aconole@redhat.com>
Tested-by: RobertX Wojciechowicz <robertx.wojciechowicz@intel.com>
Tested-by: Sean K Mooney <sean.k.mooney@intel.com>
Acked-by: Panu Matilainen <pmatilai@redhat.com>
Acked-by: Flavio Leitner <fbl@sysclose.org>
Acked-by: Daniele Di Proietto <diproiettod@vmware.com>
lib/netdev-dpdk.c