[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190422.221236.955234201498229792.davem@davemloft.net>
Date: Mon, 22 Apr 2019 22:12:36 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: idosch@...lanox.com
Cc: netdev@...r.kernel.org, jiri@...lanox.com, petrm@...lanox.com,
alexanderk@...lanox.com, mlxsw@...lanox.com
Subject: Re: [PATCH net-next 00/14] mlxsw: Shared buffer improvements
From: Ido Schimmel <idosch@...lanox.com>
Date: Mon, 22 Apr 2019 12:08:38 +0000
> 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 loss.
> In order to better communicate these configuration failures to the user,
> extack is propagated from devlink towards drivers. This is done in
> patches #1-#8.
>
> The second part of the patchset deals with the shared buffer
> configuration of the CPU port. When a packet is trapped by the device,
> it is sent across the PCI bus to the attached host CPU. From the
> device's perspective, it is as if the packet is transmitted through the
> CPU port.
>
> While testing traffic directed at the CPU it became apparent that for
> certain packet sizes and certain burst sizes, the current shared buffer
> configuration of the CPU port is inadequate and results in packet drops.
> The configuration is adjusted by patches #9-#14 that create two new pools
> - ingress & egress - which are dedicated for CPU traffic.
Series applied, thank you.
Powered by blists - more mailing lists