netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, edumazet@google.com, petrm@nvidia.com,
	mlxsw@nvidia.com
Subject: Re: [PATCH net] mlxsw: spectrum_cnt: Reorder counter pools
Date: Tue, 14 Jun 2022 14:10:15 +0000	[thread overview]
Message-ID: <165521581518.20153.5995266466532935010.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220613125017.2018162-1-idosch@nvidia.com>

Hello:

This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:

On Mon, 13 Jun 2022 15:50:17 +0300 you wrote:
> From: Petr Machata <petrm@nvidia.com>
> 
> Both RIF and ACL flow counters use a 24-bit SW-managed counter address to
> communicate which counter they want to bind.
> 
> In a number of Spectrum FW releases, binding a RIF counter is broken and
> slices the counter index to 16 bits. As a result, on Spectrum-2 and above,
> no more than about 410 RIF counters can be effectively used. This
> translates to 205 netdevices for which L3 HW stats can be enabled. (This
> does not happen on Spectrum-1, because there are fewer counters available
> overall and the counter index never exceeds 16 bits.)
> 
> [...]

Here is the summary with links:
  - [net] mlxsw: spectrum_cnt: Reorder counter pools
    https://git.kernel.org/netdev/net/c/4b7a632ac4e7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2022-06-14 14:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-13 12:50 [PATCH net] mlxsw: spectrum_cnt: Reorder counter pools Ido Schimmel
2022-06-14 14:10 ` patchwork-bot+netdevbpf [this message]

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=165521581518.20153.5995266466532935010.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.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).