All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<sgoutham@marvell.com>, <davem@davemloft.net>,
	<edumazet@google.com>, <pabeni@redhat.com>
Subject: Re: [net-next PATCH V3 02/12] octeontx2-af: Exact match support
Date: Thu, 7 Jul 2022 17:53:07 -0700	[thread overview]
Message-ID: <20220707175307.4e83ad48@kernel.org> (raw)
In-Reply-To: <20220707073353.2752279-3-rkannoth@marvell.com>

On Thu, 7 Jul 2022 13:03:43 +0530 Ratheesh Kannoth wrote:
> CN10KB silicon has support for exact match table. This table
> can be used to match maimum 64 bit value of KPU parsed output.
> Hit/non hit in exact match table can be used as a KEX key to
> NPC mcam.
> 
> This patch makes use of Exact match table to increase number of
> DMAC filters supported. NPC  mcam is no more need for each of these
> DMAC entries as will be populated in Exact match table.
> 
> This patch implements following
> 
> 1. Initialization of exact match table only for CN10KB.
> 2. Add/del/update interface function for exact match table.
> 
> Signed-off-by: Ratheesh Kannoth <rkannoth@marvell.com>

Build with C=1 (i.e. with the sparse checker) we get:

drivers/net/ethernet/marvell/octeontx2/af/rvu_npc_hash.c:558:21: warning: dubious: x & !y

could you figure out which one it is and if it can be muted?

  reply	other threads:[~2022-07-08  0:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  7:33 [net-next PATCH V3 00/12] octeontx2: Exact Match Table Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 01/12] octeontx2-af: Use hashed field in MCAM key Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 02/12] octeontx2-af: Exact match support Ratheesh Kannoth
2022-07-08  0:53   ` Jakub Kicinski [this message]
2022-07-08  4:48     ` [EXT] " Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 03/12] octeontx2-af: Exact match scan from kex profile Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 04/12] octeontx2-af: devlink configuration support Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 05/12] octeontx2-af: FLR handler for exact match table Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 06/12] octeontx2-af: Drop rules for NPC MCAM Ratheesh Kannoth
2022-07-08  0:54   ` Jakub Kicinski
2022-07-08  4:45     ` [EXT] " Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 07/12] octeontx2-af: Debugsfs support for exact match Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 08/12] octeontx2: Modify mbox request and response structures Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 09/12] octeontx2-af: Wrapper functions for MAC addr add/del/update/reset Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 10/12] octeontx2-af: Invoke exact match functions if supported Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 11/12] octeontx2-pf: Add support for exact match table Ratheesh Kannoth
2022-07-07  7:33 ` [net-next PATCH V3 12/12] octeontx2-af: Enable Exact match flag in kex profile Ratheesh Kannoth

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=20220707175307.4e83ad48@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.