From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 66617201 for ; Fri, 13 Apr 2018 01:30:47 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id CFB9921A46; Thu, 12 Apr 2018 19:30:46 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 12 Apr 2018 19:30:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=pogJy8Qbv1V6ma9gXDurQJNiFO mD8fy4ezlr5Hh/udY=; b=IcTm3pl4s1Z58PCLn8fqsqt+210UZp0rd5DsI1vVHz BR/SuN3Eo0km82zZG4IskgD6WInlt+TIBvns0S0TXBGLlrhJ2mzjVHS/+1SSKMcw YisIf1NgKZ6G0pkMpNTzuSAwZcKACKBEtDNHuaN4/D1KT6rNU0OyRctTt76fJZxT g= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=pogJy8 Qbv1V6ma9gXDurQJNiFOmD8fy4ezlr5Hh/udY=; b=EPYVnMb7NrUZF+QcsaIaJB COcZ/zu5PhBcaU4hoGtTBvJGiriw/JSlN5U5tjzgisLEnkZZO1JPKAqnZs7MLjrw 78vUGAKRIVDXqKRov9PUicKsrxPEsVbIjz/AIcejYgRH8gfGp7OUZ0pvCRDRh5Cc dki2WFhyRx60hF4viXN6G0T9cg27Ti87kCVDB4YQCJDFKffcLXMsntW4/tWYhHGK Op5+3TUhnuhQJYbsTC9UbliYRySS7IiiK27+IQGbk39ZsRmDezvBYBOC00AnbpNz jIzoh+N5QAfHI6JhpG78Wpj9Yj3cogUEO/gkpdg/5Nqy59iATg6BrMMQWvOScCdw == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 4D007E43EC; Thu, 12 Apr 2018 19:30:46 -0400 (EDT) From: Thomas Monjalon To: Jianfeng Tan Cc: dev@dpdk.org Date: Fri, 13 Apr 2018 01:30:45 +0200 Message-ID: <1561788.jEzySPKPAF@xps> In-Reply-To: <1522950303-17206-1-git-send-email-jianfeng.tan@intel.com> References: <1522950303-17206-1-git-send-email-jianfeng.tan@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 0/5] allow procinfo and pdump on eth vdev X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Apr 2018 23:30:47 -0000 Hi Jinafeng, 05/04/2018 19:44, Jianfeng Tan: > As we know, we have below limitations in vdev: > - dpdk-procinfo cannot get the stats of (most) vdev in primary process; > - dpdk-pdump cannot dump the packets for (most) vdev in primary proces; > - secondary process cannot use (most) vdev in primary process. > > The very first reason is that the secondary process actually does not know > the existence of those vdevs as vdevs are chained on a linked list, and > not shareable to secondary. > > In this patch series, we would like to propose a vdev sharing model like this: > - As a secondary process boots, all devices (including vdev) in primary > will be automatically shared. After both primary and secondary process > booted, > - Device add/remove in primary will be translated to device hog plug/unplug > event in secondary processes. (TODO) > - Device add in secondary > * If that kind of device support multi-process, the secondary will > request the primary to probe the device and the primary to share > it to the secondary. It's not necessary to have secondary-private > device in this case. (TODO) > * If that kind of device does not support multi-process, the secondary > will probe the device by itself, and the port id is shared among > all primary/secondary processes. Are you OK to consider this series for DPDK 18.08?