From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 42A441B024 for ; Wed, 10 Jan 2018 15:17:22 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jan 2018 06:17:22 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,340,1511856000"; d="scan'208";a="18154868" Received: from awalabdu-mobl.ger.corp.intel.com (HELO [163.33.228.183]) ([163.33.228.183]) by FMSMGA003.fm.intel.com with ESMTP; 10 Jan 2018 06:17:20 -0800 To: Ferruh Yigit , Remy Horton , dev@dpdk.org Cc: John McNamara , Wenzhuo Lu , Jingjing Wu References: <20180108143720.7994-1-remy.horton@intel.com> <978cf9ed-2b39-f53e-3203-19f8abc9a584@intel.com> From: Mohammad Abdul Awal Message-ID: Date: Wed, 10 Jan 2018 14:17:19 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <978cf9ed-2b39-f53e-3203-19f8abc9a584@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Subject: Re: [dpdk-dev] [PATCH v4 0/5] lib: add Port Representors 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: Wed, 10 Jan 2018 14:17:23 -0000 On 09/01/2018 22:01, Ferruh Yigit wrote: > <...> > >> 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? Right. We will rewrite these parts.