On Tue, 23 Apr 2019 09:28:02 +0200, Jiri Pirko wrote:
> Tue, Apr 23, 2019 at 07:26:06AM CEST, ido...@mellanox.com wrote:
> >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
Tue, Apr 23, 2019 at 07:26:06AM CEST, ido...@mellanox.com wrote:
>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, A
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 occupa
From: Ido Schimmel
Date: Mon, 22 Apr 2019 12:08:38 +
> This patchset includes two improvements with regards to shared buffer
> configuration in mlxsw.
>
> The first part of this patchset forbids the user from performing illegal
> shared buffer configuration that can result in unnecessary pac
On Mon, 22 Apr 2019 12:08:38 +, Ido Schimmel wrote:
> This patchset includes two improvements with regards to shared buffer
> configuration in mlxsw.
>
> The first part of this patchset forbids the user from performing illegal
> shared buffer configuration that can result in unnecessary packet
