Re: [RFC PATCH net-next 00/15] Simplify IPv4 route offload API

2019-10-02 Thread Ido Schimmel
On Wed, Oct 02, 2019 at 08:17:59PM +0200, Jiri Pirko wrote: > Wed, Oct 02, 2019 at 10:40:48AM CEST, ido...@idosch.org wrote: > >From: Ido Schimmel > > > >Today, whenever an IPv4 route is added or deleted a notification is sent > >in the FIB notification chain and it is up to offload drivers to dec

Re: [RFC PATCH net-next 00/15] Simplify IPv4 route offload API

2019-10-02 Thread Jiri Pirko
Wed, Oct 02, 2019 at 10:40:48AM CEST, ido...@idosch.org wrote: >From: Ido Schimmel > >Today, whenever an IPv4 route is added or deleted a notification is sent >in the FIB notification chain and it is up to offload drivers to decide >if the route should be programmed to the hardware or not. This is

[RFC PATCH net-next 00/15] Simplify IPv4 route offload API

2019-10-02 Thread Ido Schimmel
From: Ido Schimmel Today, whenever an IPv4 route is added or deleted a notification is sent in the FIB notification chain and it is up to offload drivers to decide if the route should be programmed to the hardware or not. This is not an easy task as in hardware routes are keyed by {prefix, prefix