Re: [PATCH net-next 0/6] net: Allow FIB notifiers to fail add and replace

2018-03-29 Thread David Ahern
On 3/29/18 2:29 AM, Ido Schimmel wrote: > Nice work, David. Ran various tests and didn't see any regressions. > > I know you already know this, but for the record, we plan to add > accounting to KVD hash resources which will eventually allow us to > return errors when resources are exceeded. Than

Re: [PATCH net-next 0/6] net: Allow FIB notifiers to fail add and replace

2018-03-29 Thread David Miller
From: David Ahern Date: Tue, 27 Mar 2018 18:21:54 -0700 > I wanted to revisit how resource overload is handled for hardware offload > of FIB entries and rules. At the moment, the in-kernel fib notifier can > tell a driver about a route or rule add, replace, and delete, but the > notifier can not

Re: [PATCH net-next 0/6] net: Allow FIB notifiers to fail add and replace

2018-03-29 Thread Ido Schimmel
On Tue, Mar 27, 2018 at 06:21:54PM -0700, David Ahern wrote: > I wanted to revisit how resource overload is handled for hardware offload > of FIB entries and rules. At the moment, the in-kernel fib notifier can > tell a driver about a route or rule add, replace, and delete, but the > notifier can n

[PATCH net-next 0/6] net: Allow FIB notifiers to fail add and replace

2018-03-27 Thread David Ahern
I wanted to revisit how resource overload is handled for hardware offload of FIB entries and rules. At the moment, the in-kernel fib notifier can tell a driver about a route or rule add, replace, and delete, but the notifier can not affect the action. Specifically, in the case of mlxsw if a route o