From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 9998F29D6 for ; Tue, 5 Sep 2017 19:44:25 +0200 (CEST) Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Sep 2017 10:44:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,480,1498546800"; d="scan'208";a="125802065" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.57]) ([10.237.220.57]) by orsmga004.jf.intel.com with ESMTP; 05 Sep 2017 10:44:23 -0700 To: Jerin Jacob , dev@dpdk.org Cc: santosh.shukla@caviumnetworks.com References: <20170831145436.5397-1-jerin.jacob@caviumnetworks.com> <20170831145436.5397-7-jerin.jacob@caviumnetworks.com> From: Ferruh Yigit Message-ID: <1a02f2ba-bbd0-bc5b-1d0d-bdbcc88f7aba@intel.com> Date: Tue, 5 Sep 2017 18:44:22 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <20170831145436.5397-7-jerin.jacob@caviumnetworks.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH 06/26] net/octeontx/base: probe PKI and PKO PCIe VF devices 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: Tue, 05 Sep 2017 17:44:26 -0000 On 8/31/2017 3:54 PM, Jerin Jacob wrote: > An octeontx ethdev device consists of multiple PKO VF devices and an PKI > VF device. On Octeontx HW, each Rx queues are enumerated as SSOVF device > which is exposed as event_octeontx device, Tx queues are enumerated as > PKOVF device, and ingress packet configuration is accomplished through > PKIVF device. > > In order to expose as an single ethdev instance, On PCIe VF probe, > the driver stores the information associated with the PCIe VF device and > later with vdev infrastructure creates ethdev device with earlier > probed PCIe VF device. So, is following correct: BGX is MAC interface, in ingress it consists of single PKIVF (packet input) device, in egress it consists of PKOVF (packet output) devices. PKIVF and PKOVF are physical eventdev devices. First physical devices are probed, later virtual ethdev is created which gets/puts packets into these event devices. A graph in documentation can be very helpful for this. Also patchset can create multiple ethdev ports, why is this? And how eventdev - ethdev port mapping done for that case? Thanks, ferruh > > Signed-off-by: Jerin Jacob > Co-authored-by: Santosh Shukla <...>