From: Subbaraya Sundeep <sbhatta@marvell.com>
To: Simon Horman <horms@kernel.org>
Cc: <andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<gakula@marvell.com>, <hkelam@marvell.com>,
<bbhushan2@marvell.com>, <jerinj@marvell.com>,
<lcherian@marvell.com>, <sgoutham@marvell.com>,
<netdev@vger.kernel.org>
Subject: Re: [net-next PATCH v3 01/11] octeontx2-af: Simplify context writing and reading to hardware
Date: Thu, 24 Jul 2025 14:50:40 +0000 [thread overview]
Message-ID: <aIJIQDtlx7WJtftf@opensource> (raw)
In-Reply-To: <20250722162950.GO2459@horms.kernel.org>
Hi Simon,
On 2025-07-22 at 16:29:50, Simon Horman (horms@kernel.org) wrote:
> On Tue, Jul 22, 2025 at 05:27:43PM +0100, Simon Horman wrote:
> > On Thu, Jul 17, 2025 at 10:37:33PM +0530, Subbaraya Sundeep wrote:
> > > Simplify NIX context reading and writing by using hardware
> > > maximum context size instead of using individual sizes of
> > > each context type.
> > >
> > > Signed-off-by: Subbaraya Sundeep <sbhatta@marvell.com>
> >
> > ...
> >
> > > diff --git a/drivers/net/ethernet/marvell/octeontx2/af/rvu_struct.h b/drivers/net/ethernet/marvell/octeontx2/af/rvu_struct.h
> > > index 0596a3ac4c12..1097c86fdc46 100644
> > > --- a/drivers/net/ethernet/marvell/octeontx2/af/rvu_struct.h
> > > +++ b/drivers/net/ethernet/marvell/octeontx2/af/rvu_struct.h
> > > @@ -13,6 +13,8 @@
> > >
> > > #define RVU_MULTI_BLK_VER 0x7ULL
> > >
> > > +#define NIX_MAX_CTX_SIZE 128
> > > +
> > > /* RVU Block Address Enumeration */
> > > enum rvu_block_addr_e {
> > > BLKADDR_RVUM = 0x0ULL,
> > > @@ -370,8 +372,12 @@ struct nix_cq_ctx_s {
> > > u64 qsize : 4;
> > > u64 cq_err_int : 8;
> > > u64 cq_err_int_ena : 8;
> > > + /* Ensure all context sizes are minimum 128 bytes */
> >
> > Would this be better phrased as follows?
> >
> > /* Ensure all context sizes are 128 bytes */
> >
> > > + u64 padding[12];
> > > };
> > >
> > > +static_assert(sizeof(struct nix_cq_ctx_s) == NIX_MAX_CTX_SIZE);
> >
> > I would suggest adding +static_assert() for all the
> > drivers that you expect to be NIX_MAX_CTX_SIZE.
> >
> > So also:
> > - struct nix_rq_ctx_s
> > - struct nix_sq_ctx_s
> > - struct nix_bandprof_s
>
> Likewise for new structures added by subsequent patches.
Sure. I will add for all structures
Thanks,
Sundeep
>
> ...
next prev parent reply other threads:[~2025-07-24 14:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 17:07 [net-next PATCH v3 00/11] Add CN20K NIX and NPA contexts Subbaraya Sundeep
2025-07-17 17:07 ` [net-next PATCH v3 01/11] octeontx2-af: Simplify context writing and reading to hardware Subbaraya Sundeep
2025-07-22 16:27 ` Simon Horman
2025-07-22 16:29 ` Simon Horman
2025-07-24 14:50 ` Subbaraya Sundeep [this message]
2025-07-17 17:07 ` [net-next PATCH v3 02/11] octeontx2-af: Add cn20k NIX block contexts Subbaraya Sundeep
2025-07-17 17:07 ` [net-next PATCH v3 03/11] octeontx2-af: Extend debugfs support for cn20k NIX Subbaraya Sundeep
2025-07-22 16:40 ` Simon Horman
2025-07-24 14:51 ` Subbaraya Sundeep
2025-07-17 17:07 ` [net-next PATCH v3 04/11] octeontx2-af: Add cn20k NPA block contexts Subbaraya Sundeep
2025-07-17 17:07 ` [net-next PATCH v3 05/11] octeontx2-af: Extend debugfs support for cn20k NPA Subbaraya Sundeep
2025-07-17 17:07 ` [net-next PATCH v3 06/11] octeontx2-af: Skip NDC operations for cn20k Subbaraya Sundeep
2025-07-17 17:07 ` [net-next PATCH v3 07/11] octeontx2-pf: Initialize cn20k specific aura and pool contexts Subbaraya Sundeep
2025-07-22 0:40 ` Jakub Kicinski
2025-07-22 17:03 ` Simon Horman
2025-07-24 14:54 ` Subbaraya Sundeep
2025-07-17 17:07 ` [net-next PATCH v3 08/11] octeontx2-pf: Initialize new NIX SQ context for cn20k Subbaraya Sundeep
2025-07-22 17:06 ` Simon Horman
2025-07-24 14:57 ` Subbaraya Sundeep
2025-07-17 17:07 ` [net-next PATCH v3 09/11] octeontx2-af: Accommodate more bandwidth profiles " Subbaraya Sundeep
2025-07-22 17:08 ` Simon Horman
2025-07-24 14:58 ` Subbaraya Sundeep
2025-07-17 17:07 ` [net-next PATCH v3 10/11] octeontx2-af: Display new bandwidth profiles too in debugfs Subbaraya Sundeep
2025-07-17 17:07 ` [net-next PATCH v3 11/11] octeontx2-pf: Use new bandwidth profiles in receive queue Subbaraya Sundeep
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aIJIQDtlx7WJtftf@opensource \
--to=sbhatta@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgoutham@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).