Re: [PATCH net-next] sfc: get rid of custom busy polling code

2017-02-03 Thread David Miller
From: Eric Dumazet Date: Thu, 02 Feb 2017 17:13:19 -0800 > From: Eric Dumazet > > In linux-4.5, busy polling was implemented in core > NAPI stack, meaning that all custom implementation can > be removed from drivers. > > Not only we remove lot's of tricky code, we also remove > one lock operat

Re: [PATCH net-next] sfc: get rid of custom busy polling code

2017-02-03 Thread Eric Dumazet
On Fri, 2017-02-03 at 09:14 +, Bert Kenward wrote: > On 03/02/17 01:13, Eric Dumazet wrote: > > From: Eric Dumazet > > > > In linux-4.5, busy polling was implemented in core > > NAPI stack, meaning that all custom implementation can > > be removed from drivers. > > > > Not only we remove lot

Re: [PATCH net-next] sfc: get rid of custom busy polling code

2017-02-03 Thread Bert Kenward
On 03/02/17 01:13, Eric Dumazet wrote: > From: Eric Dumazet > > In linux-4.5, busy polling was implemented in core > NAPI stack, meaning that all custom implementation can > be removed from drivers. > > Not only we remove lot's of tricky code, we also remove > one lock operation in fast path. >

[PATCH net-next] sfc: get rid of custom busy polling code

2017-02-02 Thread Eric Dumazet
From: Eric Dumazet In linux-4.5, busy polling was implemented in core NAPI stack, meaning that all custom implementation can be removed from drivers. Not only we remove lot's of tricky code, we also remove one lock operation in fast path. Signed-off-by: Eric Dumazet Cc: Edward Cree Cc: Bert K