From mboxrd@z Thu Jan 1 00:00:00 1970 From: Qi Zhang Subject: [PATCH v3 0/2] fix pcap handlers for secondary Date: Thu, 15 Nov 2018 03:56:45 +0800 Message-ID: <20181114195647.196648-1-qi.z.zhang@intel.com> References: <20181105210823.38757-1-qi.z.zhang@intel.com> Cc: thomas@monjalon.net, dev@dpdk.org, xueqin.lin@intel.com, Qi Zhang To: ferruh.yigit@intel.com Return-path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id AA4621B207 for ; Wed, 14 Nov 2018 20:55:35 +0100 (CET) In-Reply-To: <20181105210823.38757-1-qi.z.zhang@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Private vdev was the way previously, when pdump developed, now with shared device mode on virtual devices, pcap data path in secondary is not working. When secondary adds a virtual device, related data transferred to primary and primary creates the device and shares device back with secondary. When pcap device created in primary, pcap handlers (pointers) are process local and they are not valid for secondary process. This breaks secondary. So we can't directly share the pcap handlers, but need to create a new set of handlers for secondary, that's what we done in this patch. Also so we use `rte_eth_dev->process_private` to store pcap handlers separately for each process, so a handler in one process will not be closed or overwritten by another process unexpectedly. Qi Zhang (2): net/pcap: move pcap handler to process private net/pcap: enable data path for secondary drivers/net/pcap/rte_eth_pcap.c | 101 ++++++++++++++++++++++++++++++++++------ 1 file changed, 86 insertions(+), 15 deletions(-) -- 2.13.6