Assign correct NUMA node for DPDK crypto devices

DPDK rte_cryptodev_socket_id() is returning zero for QAT devices.
Apply DPDK patch where correct NUMA node can be obtained with pci_dev->device.numa_node.

Change-Id: I1c7a77bb13e2db8615189e97b67d68d043127787
Signed-off-by: Lee Roberts <lee.roberts@hpe.com>

dpdk/dpdk-18.02_patches/0001-assign-QAT-cryptodev-to-correct-NUMA-node.patch

@@ -0,0 +1,29 @@
+From b01857dfdb4e46b8c7d306c608c58ebbabc252ec Mon Sep 17 00:00:00 2001
+From: Lee Roberts <lee.roberts@hpe.com>
+Date: Fri, 9 Mar 2018 10:49:34 -0700
+Subject: [PATCH] assign QAT cryptodev to correct NUMA node
+
+rte_cryptodev_pmd_init_params should use NUMA node of the QAT device
+for its socket_id rather than the socket_id of the initializing process.
+
+Signed-off-by: Lee Roberts <lee.roberts@hpe.com>
+---
+ drivers/crypto/qat/rte_qat_cryptodev.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/drivers/crypto/qat/rte_qat_cryptodev.c b/drivers/crypto/qat/rte_qat_cryptodev.c
+index bf83740..82641aa 100644
+--- a/drivers/crypto/qat/rte_qat_cryptodev.c
++++ b/drivers/crypto/qat/rte_qat_cryptodev.c
+@@ -130,7 +130,7 @@ static int crypto_qat_pci_probe(struct rte_pci_driver *pci_drv __rte_unused,
+ {
+ 	struct rte_cryptodev_pmd_init_params init_params = {
+ 		.name = "",
+-		.socket_id = rte_socket_id(),
++		.socket_id = pci_dev->device.numa_node,
+ 		.private_data_size = sizeof(struct qat_pmd_private),
+ 		.max_nb_sessions = RTE_QAT_PMD_MAX_NB_SESSIONS
+ 	};
+-- 
+1.9.1
+