[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241207183824.4a306105@kernel.org>
Date: Sat, 7 Dec 2024 18:38:24 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Sai Krishna <saikrishnag@...vell.com>
Cc: <davem@...emloft.net>, <edumazet@...gle.com>, <pabeni@...hat.com>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<sgoutham@...vell.com>, <gakula@...vell.com>, <lcherian@...vell.com>,
<jerinj@...vell.com>, <hkelam@...vell.com>, <sbhatta@...vell.com>,
<andrew+netdev@...n.ch>, <kalesh-anakkur.purayil@...adcom.com>
Subject: Re: [net-next PATCH v5 1/6] octeontx2: Set appropriate PF, VF masks
and shifts based on silicon
On Wed, 4 Dec 2024 19:38:16 +0530 Sai Krishna wrote:
> -#define RVU_PFVF_PF_SHIFT 10
> -#define RVU_PFVF_PF_MASK 0x3F
> -#define RVU_PFVF_FUNC_SHIFT 0
> -#define RVU_PFVF_FUNC_MASK 0x3FF
> +#define RVU_PFVF_PF_SHIFT rvu_pcifunc_pf_shift
> +#define RVU_PFVF_PF_MASK rvu_pcifunc_pf_mask
> +#define RVU_PFVF_FUNC_SHIFT rvu_pcifunc_func_shift
> +#define RVU_PFVF_FUNC_MASK rvu_pcifunc_func_mask
Why do you maintain these defines? Looks like an unnecessary
indirection.
Given these are simple mask and shift values they probably have trivial
users. Start by adding helpers which perform the conversions using
those, then you can more easily update constants.
Powered by blists - more mailing lists