From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v3 18/29] net/cxgbe: use eal I/O device memory read/write API Date: Thu, 12 Jan 2017 19:12:33 +0000 Message-ID: References: <1482832175-27199-1-git-send-email-jerin.jacob@caviumnetworks.com> <1484212646-10338-1-git-send-email-jerin.jacob@caviumnetworks.com> <1484212646-10338-19-git-send-email-jerin.jacob@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: konstantin.ananyev@intel.com, thomas.monjalon@6wind.com, bruce.richardson@intel.com, jianbo.liu@linaro.org, viktorin@rehivetech.com, santosh.shukla@caviumnetworks.com, Rahul Lakkireddy To: Jerin Jacob , dev@dpdk.org Return-path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 02C37F618 for ; Thu, 12 Jan 2017 20:13:13 +0100 (CET) In-Reply-To: <1484212646-10338-19-git-send-email-jerin.jacob@caviumnetworks.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 1/12/2017 9:17 AM, Jerin Jacob wrote: <...> > > -#define CXGBE_PCI_REG_WRITE(reg, value) ({ \ > - CXGBE_PCI_REG((reg)) = (value); }) > +#define CXGBE_PCI_REG_WRITE(reg, value) rte_write32((value), (reg)) Almost all (if not all) PMD write macros' argument order is like write(address, value), but rte_writeX has rte_writex(value, address) What is the common usage for this kind of function? What do you think reverting argument order? As a similar example, dpdk ether_addr_copy(src, dst) function argument order is revers according common usage, and keeps confusing people. <...>