From: Ido Schimmel <idosch@mellanox.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
Jiri Pirko <jiri@mellanox.com>, Petr Machata <petrm@mellanox.com>,
Alex Kushnarov <alexanderk@mellanox.com>,
mlxsw <mlxsw@mellanox.com>
Subject: Re: [PATCH net-next 00/14] mlxsw: Shared buffer improvements
Date: Tue, 23 Apr 2019 05:26:06 +0000 [thread overview]
Message-ID: <20190423052602.GA1735@splinter> (raw)
In-Reply-To: <20190422141739.4812894b@cakuba.netronome.com>
On Mon, Apr 22, 2019 at 02:17:39PM -0700, Jakub Kicinski wrote:
> Out of curiosity - are you guys considering adding CPU flavour ports,
> or is there a good reason not to have it exposed?
Yes, we are considering that. In fact, Alexander (Cc-ed) just asked me if
it is possible to monitor the occupancy in the egress CPU pool. This is
impossible without exposing the CPU port and it would have saved us a
lot of time while debugging these issues.
Do you need this functionality for nfp as well? If so, do you have any
thoughts about it? My thinking is that it would be a devlink port
without a backing netdev.
next prev parent reply other threads:[~2019-04-23 5:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 12:08 [PATCH net-next 00/14] mlxsw: Shared buffer improvements Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 01/14] net: devlink: Add extack to shared buffer operations Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 02/14] mlxsw: spectrum_buffers: Add extack messages for invalid configurations Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 03/14] mlxsw: spectrum_buffers: Use defines for pool indices Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 04/14] mlxsw: spectrum_buffers: Add ability to veto pool's configuration Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 05/14] mlxsw: spectrum_buffers: Add ability to veto TC's configuration Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 06/14] mlxsw: spectrum_buffers: Forbid configuration of multicast pool Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 07/14] mlxsw: spectrum_buffers: Forbid changing threshold type of first egress pool Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 08/14] mlxsw: spectrum_buffers: Forbid changing multicast TCs' attributes Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 09/14] mlxsw: spectrum_buffers: Remove assumption about pool order Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 10/14] mlxsw: spectrum_buffers: Add pools for CPU traffic Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 11/14] mlxsw: spectrum_buffers: Use new CPU ingress pool for control packets Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 12/14] mlxsw: spectrum_buffers: Split business logic from mlxsw_sp_port_sb_pms_init() Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 13/14] mlxsw: spectrum_buffers: Allow skipping ingress port quota configuration Ido Schimmel
2019-04-22 12:08 ` [PATCH net-next 14/14] mlxsw: spectrum_buffers: Adjust CPU port shared buffer egress quotas Ido Schimmel
2019-04-22 21:17 ` [PATCH net-next 00/14] mlxsw: Shared buffer improvements Jakub Kicinski
2019-04-23 5:26 ` Ido Schimmel [this message]
2019-04-23 7:28 ` Jiri Pirko
2019-04-23 16:31 ` Jakub Kicinski
2019-04-23 5:12 ` David Miller
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=20190423052602.GA1735@splinter \
--to=idosch@mellanox.com \
--cc=alexanderk@mellanox.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.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.