On 9/8/2020 5:04 PM, Jiri Pirko wrote:
Sun, Sep 06, 2020 at 05:44:28PM CEST, ido...@idosch.org wrote:
On Wed, Sep 02, 2020 at 06:32:12PM +0300, Aya Levin wrote:
[...]
I understand how this struct allows you to re-use a lot of code between
per-device and per-port traps, but it's mainly en
Sun, Sep 06, 2020 at 05:44:28PM CEST, ido...@idosch.org wrote:
>On Wed, Sep 02, 2020 at 06:32:12PM +0300, Aya Levin wrote:
[...]
>
>I understand how this struct allows you to re-use a lot of code between
>per-device and per-port traps, but it's mainly enabled by the fact that
>you use the same ne
On 9/6/2020 6:44 PM, Ido Schimmel wrote:
On Wed, Sep 02, 2020 at 06:32:12PM +0300, Aya Levin wrote:
There are some cases where we would like to trap dropped packets only
for a single port on a device without affecting the others. For that
purpose trap_mngr was added to devlink_port and corres
On Wed, Sep 02, 2020 at 06:32:12PM +0300, Aya Levin wrote:
> There are some cases where we would like to trap dropped packets only
> for a single port on a device without affecting the others. For that
> purpose trap_mngr was added to devlink_port and corresponding Trap API
> with devlink_port were
There are some cases where we would like to trap dropped packets only
for a single port on a device without affecting the others. For that
purpose trap_mngr was added to devlink_port and corresponding Trap API
with devlink_port were added too.
Signed-off-by: Aya Levin
---
drivers/net/ethernet/me
