thr3ads.net - search: "mlxsw"

[Bridge] [RFC PATCH net-next 0/5] Add layer 2 miss indication and filtering

2023 May 09

5

[Bridge] [RFC PATCH net-next 0/5] Add layer 2 miss indication and filtering

...ting hole in the skb in order not to inflate this data structure. Patch #2 extends the flower classifier to be able to match on the new layer 2 miss metadata. Patch #3 rejects matching on the new metadata in drivers that already support the 'FLOW_DISSECTOR_KEY_META' key. Patch #4 extends mlxsw to be able to match on layer 2 miss. Patch #5 adds a selftest. iproute2 patches can be found here [3]. [1] https://datatracker.ietf.org/doc/html/rfc7432#section-8.3 [2] https://datatracker.ietf.org/doc/html/rfc7432#section-8.5 [3] https://github.com/idosch/iproute2/tree/submit/non_df_filter_v1...

[Bridge] [PATCH net-next 0/5] Add layer 2 miss indication and filtering

2023 May 18

5

[Bridge] [PATCH net-next 0/5] Add layer 2 miss indication and filtering

...ting hole in the skb in order not to inflate this data structure. Patch #2 extends the flower classifier to be able to match on the new layer 2 miss metadata. Patch #3 rejects matching on the new metadata in drivers that already support the 'FLOW_DISSECTOR_KEY_META' key. Patch #4 extends mlxsw to be able to match on layer 2 miss. Patch #5 adds a selftest. iproute2 patches can be found here [3]. Changelog ========= Since RFC [4]: No changes. [1] https://datatracker.ietf.org/doc/html/rfc7432#section-8.3 [2] https://datatracker.ietf.org/doc/html/rfc7432#section-8.5 [3] https://github....

[Bridge] [RFC PATCH net-next 3/5] flow_offload: Reject matching on layer 2 miss

2023 May 09

1

[Bridge] [RFC PATCH net-next 3/5] flow_offload: Reject matching on layer 2 miss

...39;FLOW_DISSECTOR_KEY_META' key to reject filters that try to match on the newly added layer 2 miss option. Add an extack message to clearly communicate the failure reason to user space. Example: # tc filter add dev swp1 egress pref 1 proto all flower skip_sw l2_miss true action drop Error: mlxsw_spectrum: Can't match on "l2_miss". We have an error talking to the kernel Signed-off-by: Ido Schimmel <idosch at nvidia.com> --- .../net/ethernet/marvell/prestera/prestera_flower.c | 6 ++++++ drivers/net/ethernet/mellanox/mlx5/core/en_tc.c | 6 ++++++ drivers/ne...

[PATCH net-next] net: make ndo_get_stats64 a void function

2017 Jan 05

3

[PATCH net-next] net: make ndo_get_stats64 a void function

...| 6 ++---- drivers/net/ethernet/mediatek/mtk_eth_soc.c | 6 ++---- drivers/net/ethernet/mellanox/mlx4/en_netdev.c | 4 +--- drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 3 +-- drivers/net/ethernet/mellanox/mlx5/core/en_rep.c | 3 +-- drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 4 +--- drivers/net/ethernet/mellanox/mlxsw/switchx2.c | 3 +-- drivers/net/ethernet/myricom/myri10ge/myri10ge.c | 9 ++++----- drivers/net/ethernet/neterion/vxge/vxge-main.c | 4 +--- drivers/net/ethernet/netronome/nfp/nfp_net_common.c | 6 ++---- drivers/n...

[PATCH net-next] net: make ndo_get_stats64 a void function

2017 Jan 05

3

[PATCH net-next] net: make ndo_get_stats64 a void function

...| 6 ++---- drivers/net/ethernet/mediatek/mtk_eth_soc.c | 6 ++---- drivers/net/ethernet/mellanox/mlx4/en_netdev.c | 4 +--- drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 3 +-- drivers/net/ethernet/mellanox/mlx5/core/en_rep.c | 3 +-- drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 4 +--- drivers/net/ethernet/mellanox/mlxsw/switchx2.c | 3 +-- drivers/net/ethernet/myricom/myri10ge/myri10ge.c | 9 ++++----- drivers/net/ethernet/neterion/vxge/vxge-main.c | 4 +--- drivers/net/ethernet/netronome/nfp/nfp_net_common.c | 6 ++---- drivers/n...

[RFC PATCH 2/3] netdev: kernel-only IFF_HIDDEN netdevice

2018 Apr 04

0

[RFC PATCH 2/3] netdev: kernel-only IFF_HIDDEN netdevice

...v should not be mucked with > by a user. It should be ignored by certain s/w with lldpd as just an > *example*. Two approaches: 1) Add an IFF_CONTROL and make userspace understand this. It is probably long overdue. 2) Design the driver properly. Have a non-netdev master device like mlxsw does, and control it using devlink or similar. This is exactly how this stuff was meant to be architected. > From there I think you are confusing my intentions: I fundamentally do > not believe the kernel should be hiding anything from an admin. Not > showing data by default is comple...

[PATCH -next 000/491] treewide: use fallthrough;

2020 Mar 11

0