From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH 00/28] introduce I/O device memory read/write operations Date: Wed, 14 Dec 2016 10:12:44 +0000 Message-ID: <20161214101244.GA94040@bricha3-MOBL3.ger.corp.intel.com> References: <1481680558-4003-1-git-send-email-jerin.jacob@caviumnetworks.com> <20161214025357.GF18991@yliu-dev.sh.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jerin Jacob , dev@dpdk.org, konstantin.ananyev@intel.com, thomas.monjalon@6wind.com, jianbo.liu@linaro.org, viktorin@rehivetech.com To: Yuanhan Liu Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 7DE5D370 for ; Wed, 14 Dec 2016 11:12:48 +0100 (CET) Content-Disposition: inline In-Reply-To: <20161214025357.GF18991@yliu-dev.sh.intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, Dec 14, 2016 at 10:53:57AM +0800, Yuanhan Liu wrote: > On Wed, Dec 14, 2016 at 07:25:30AM +0530, Jerin Jacob wrote: > > patchset 14-28: Replace the raw readl/writel in the drivers with > > new rte_read[b/w/l/q], rte_write[b/w/l/q] eal abstraction > > Instead of rte_read[b/w/l/q], there is another typical naming style: > rte_read[8/16/32/64]. Any preferences? If you ask me, I'd prefer the > later. > I think I prefer the latter too, as it aligns with our naming of atomic functions and our use of uint16_t etc. types. /Bruce