From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v4 0/5] lib: add Port Representors Date: Tue, 9 Jan 2018 22:01:56 +0000 Message-ID: <978cf9ed-2b39-f53e-3203-19f8abc9a584@intel.com> References: <20180108143720.7994-1-remy.horton@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: John McNamara , Wenzhuo Lu , Jingjing Wu To: Remy Horton , dev@dpdk.org Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 3632D1B1B5 for ; Tue, 9 Jan 2018 23:01:59 +0100 (CET) In-Reply-To: <20180108143720.7994-1-remy.horton@intel.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" <...> > The port representor infrastructure is enabled through a single common, device > independent, virtual PMD whos context is initialized and enabled through a > broker instance running within the context of the physical function device > driver.> > +-------------------------+ +-------------------------+ > | rte_ethdev | | rte_ethdev | > +-------------------------+ +-------------------------+ > | Physical Function PMD | | Port Reperesentor PMD | > | +-------------+ | | +---------+ +---------+ | > | | Representor | | | | dev_data| | dev_ops | | > | | Broker | | | +----+----+ +----+----+ | > | | +---------+ | | +------|-----------|------+ > | | | VF Port | | | | | > | | | Context +------------------+ | > | | +---------+ | | | > | | +---------+ | | | > | | | Handler +------------------------------+ > | | | Ops | | | > | | +---------+ | | > | +-------------+ | > +-------------------------+ > > Creation of representor ports can be achieved either through the --vdev EAL > option or through the rte_vdev_init() API. Each port representor requires the > BDF of it's parent PF and the Virtual Function ID of the port which the > representor will support. During initialization of the representor PMD, it calls > the broker API to register itself with the PF PMD and to get it's context > configured which includes the setting up of it's context and ops function > handlers. Above no more true, right?