From: Simon Horman <horms@kernel•org>
To: Mohsin Bashir <mohsin.bashr@gmail•com>
Cc: netdev@vger•kernel.org, alexanderduyck@fb•com, kuba@kernel•org,
andrew@lunn•ch, andrew+netdev@lunn•ch, davem@davemloft•net,
edumazet@google•com, pabeni@redhat•com, kernel-team@meta•com,
sanmanpradhan@meta•com, sdf@fomichev•me,
vadim.fedorenko@linux•dev
Subject: Re: [PATCH net-next v2] eth: fbnic: Add support to write TCE TCAM entries
Date: Fri, 25 Oct 2024 13:52:46 +0100 [thread overview]
Message-ID: <20241025125246.GS1202098@kernel.org> (raw)
In-Reply-To: <20241024223135.310733-1-mohsin.bashr@gmail.com>
On Thu, Oct 24, 2024 at 03:31:35PM -0700, Mohsin Bashir wrote:
> Add support for writing to the tce tcam to enable host to bmc traffic.
> Currently, we lack metadata to track where addresses have been written
> in the tcam, except for the last entry written. To address this issue,
> we start at the opposite end of the table in each pass, so that adding
> or deleting entries does not affect the availability of all entries,
> assuming there is no significant reordering of entries.
>
> Signed-off-by: Mohsin Bashir <mohsin.bashr@gmail•com>
> ---
> V2:
> - Fixed spelling error from 'entrie' to 'entries' in the summary.
>
> V1: https://lore.kernel.org/netdev/20241021185544.713305-1-mohsin.bashr@gmail.com
Thanks for the update.
Reviewed-by: Simon Horman <horms@kernel•org>
next prev parent reply other threads:[~2024-10-25 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 22:31 [PATCH net-next v2] eth: fbnic: Add support to write TCE TCAM entries Mohsin Bashir
2024-10-25 12:52 ` Simon Horman [this message]
2024-10-25 15:19 ` Alexander Lobakin
2024-10-28 23:35 ` Jakub Kicinski
2024-10-29 15:30 ` Alexander Lobakin
2024-10-30 0:26 ` Jakub Kicinski
2024-10-30 18:34 ` Andrew Lunn
2024-10-31 1:19 ` Mohsin Bashir
[not found] ` <97383310-c846-493a-a023-4d8033c5680b@gmail.com>
2024-10-31 12:43 ` Andrew Lunn
2024-10-31 22:13 ` Mohsin Bashir
2024-11-01 12:33 ` Andrew Lunn
2024-11-01 23:04 ` Alexander H Duyck
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=20241025125246.GS1202098@kernel.org \
--to=horms@kernel$(echo .)org \
--cc=alexanderduyck@fb$(echo .)com \
--cc=andrew+netdev@lunn$(echo .)ch \
--cc=andrew@lunn$(echo .)ch \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=kernel-team@meta$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=mohsin.bashr@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=sanmanpradhan@meta$(echo .)com \
--cc=sdf@fomichev$(echo .)me \
--cc=vadim.fedorenko@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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