lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 14 Jan 2020 17:41:02 +0100 From: Jiri Pirko <jiri@...nulli.us> To: Ido Schimmel <idosch@...sch.org> Cc: netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org, jiri@...lanox.com, dsahern@...il.com, roopa@...ulusnetworks.com, mlxsw@...lanox.com, Ido Schimmel <idosch@...lanox.com> Subject: Re: [PATCH net-next v2 06/10] mlxsw: spectrum_router: Set hardware flags for routes Tue, Jan 14, 2020 at 12:23:14PM CET, idosch@...sch.org wrote: >From: Ido Schimmel <idosch@...lanox.com> > >Previous patches added support for two hardware flags for IPv4 and IPv6 >routes: 'RTM_F_OFFLOAD' and 'RTM_F_TRAP'. Both indicate the presence of >the route in hardware. The first indicates that traffic is actually >offloaded from the kernel, whereas the second indicates that packets >hitting such routes are trapped to the kernel for processing (e.g., host >routes). > >Use these two flags in mlxsw. The flags are modified in two places. >Firstly, whenever a route is updated in the device's table. This >includes the addition, deletion or update of a route. For example, when >a host route is promoted to perform NVE decapsulation, its action in the >device is updated, the 'RTM_F_OFFLOAD' flag set and the 'RTM_F_TRAP' >flag cleared. > >Secondly, when a route is replaced and overwritten by another route, its >flags are cleared. > >v2: >* Convert to new fib_alias_hw_flags_set() interface > >Signed-off-by: Ido Schimmel <idosch@...lanox.com> Acked-by: Jiri Pirko <jiri@...lanox.com>
Powered by blists - more mailing lists