Re: [patch net-next 2/4] net: sched: introduce per-egress action device callbacks

2017-10-10 Thread Jiri Pirko
nox.com; mat...@mellanox.com; leo...@mellanox.com; >> ml...@mellanox.com >> Subject: Re: [patch net-next 2/4] net: sched: introduce per-egress action >> device callbacks >> >> Tue, Oct 10, 2017 at 03:31:59PM CEST, david.lai...@aculab.com wrote: >> >From: Jiri Pir

RE: [patch net-next 2/4] net: sched: introduce per-egress action device callbacks

2017-10-10 Thread David Laight
From: Jiri Pirko > Sent: 10 October 2017 15:32 > To: David Laight > Cc: netdev@vger.kernel.org; da...@davemloft.net; j...@mojatatu.com; > xiyou.wangc...@gmail.com; > sae...@mellanox.com; mat...@mellanox.com; leo...@mellanox.com; > ml...@mellanox.com > Subject: Re: [patch net

Re: [patch net-next 2/4] net: sched: introduce per-egress action device callbacks

2017-10-10 Thread Jiri Pirko
Tue, Oct 10, 2017 at 03:31:59PM CEST, david.lai...@aculab.com wrote: >From: Jiri Pirko >> Sent: 10 October 2017 08:30 >> Introduce infrastructure that allows drivers to register callbacks that >> are called whenever tc would offload inserted rule and specified device >> acts as tc action egress dev

RE: [patch net-next 2/4] net: sched: introduce per-egress action device callbacks

2017-10-10 Thread David Laight
From: Jiri Pirko > Sent: 10 October 2017 08:30 > Introduce infrastructure that allows drivers to register callbacks that > are called whenever tc would offload inserted rule and specified device > acts as tc action egress device. How does a driver safely unregister a callback? (to avoid a race wit