From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 27CE05A4C for ; Tue, 5 Jul 2016 17:47:40 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP; 05 Jul 2016 08:47:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,580,1459839600"; d="scan'208";a="1011307834" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.220.53]) by orsmga002.jf.intel.com with SMTP; 05 Jul 2016 08:47:35 -0700 Received: by (sSMTP sendmail emulation); Tue, 05 Jul 2016 16:47:35 +0025 Date: Tue, 5 Jul 2016 16:47:34 +0100 From: Bruce Richardson To: Jan =?utf-8?Q?M=C4=99dala?= Cc: dev@dpdk.org, ferruh.yigit@intel.com, Alexander Matushevsky , Jakub Palider Message-ID: <20160705154734.GA26504@bricha3-MOBL3> References: <1466510763-19569-6-git-send-email-jan@semihalf.com> <1467299099-32498-1-git-send-email-jan@semihalf.com> <1467299099-32498-4-git-send-email-jan@semihalf.com> <20160704154303.GA23380@bricha3-MOBL3> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH v3 3/6] ena: disable readless communication regarding to HW revision X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2016 15:47:41 -0000 On Tue, Jul 05, 2016 at 12:02:41PM +0200, Jan Mędala wrote: > Bruce, > > Here's explanation of readless communication (on behalf of Alex): > > > "readless" refers to ability to read ENA registers without actually > > issuing read request from host (x86). > > Instead, host programs 2 registers on device that trigger DMA from device > > to host and report register value. > > However, this functionality is not going to be available in all type of > > devices. The decision if this mode is supported or not , is taken from > > revision_id in pci configuration space. > > Thanks, I'll add this into the commit message to help explain things to anyone looking at the commit later. /Bruce > Regards > > Jan > > 2016-07-04 17:43 GMT+02:00 Bruce Richardson : > > > On Thu, Jun 30, 2016 at 05:04:56PM +0200, Jan Medala wrote: > > > Depending on HW revision readless communcation between host and device > > > may be unavailable. > > > In that case prevent PMD of seting up readless communication mechanism. > > > > > The idea of readless communication is a strange one. Can you provide a bit > > more detail as to what "readless communication" refers to. > > > > /Bruce > >