From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shreyansh Jain Subject: Re: [PATCH 01/38] eal: add support for 24 40 and 48 bit operations Date: Fri, 16 Jun 2017 09:21:35 +0000 Message-ID: References: <1497591668-3320-1-git-send-email-shreyansh.jain@nxp.com> <1497591668-3320-2-git-send-email-shreyansh.jain@nxp.com> <20170616085719.GB82628@bricha3-MOBL3.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" , "ferruh.yigit@intel.com" , Hemant Agrawal To: Bruce Richardson Return-path: Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00071.outbound.protection.outlook.com [40.107.0.71]) by dpdk.org (Postfix) with ESMTP id 936243251 for ; Fri, 16 Jun 2017 11:22:01 +0200 (CEST) In-Reply-To: <20170616085719.GB82628@bricha3-MOBL3.ger.corp.intel.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Bruce, > -----Original Message----- > From: Bruce Richardson [mailto:bruce.richardson@intel.com] > Sent: Friday, June 16, 2017 2:27 PM > To: Shreyansh Jain > Cc: dev@dpdk.org; ferruh.yigit@intel.com; Hemant Agrawal > > Subject: Re: [dpdk-dev] [PATCH 01/38] eal: add support for 24 40 and 48 b= it > operations >=20 > On Fri, Jun 16, 2017 at 11:10:31AM +0530, Shreyansh Jain wrote: > > From: Hemant Agrawal > > > > Bit Swap and LE<=3D>BE conversions for 23, 40 and 48 bit width > > > > Signed-off-by: Hemant Agrawal > > --- > > .../common/include/generic/rte_byteorder.h | 78 > ++++++++++++++++++++++ > > 1 file changed, 78 insertions(+) > > > Are these really common enough for inclusion in an generic EAL file? > Would they be better being driver specific, so that we don't end up with > lots of extra byte-swap routines for each possible size used by a > driver. =20 Reasoning was to keep all bit/byte swap at a single place and if it is useful for others. >>From DPAA perspective, these macro can be anywhere. In case someone else to= o has use of this (now or in near-future), probably then we can consider this in EAL. Else, if I don't get much responses in a few days, I will shift them to DPAA driver in next version of this series. - Shreyansh