Re: [net-next 04/13] net/mlx5e: Vxlan, replace spinlock with read-write lock

2018-07-27 Thread Saeed Mahameed
On Fri, Jul 27, 2018 at 2:48 PM, Stephen Hemminger wrote: > On Fri, 27 Jul 2018 14:15:09 -0700 > Saeed Mahameed wrote: > >> From: Gal Pressman >> >> The VXLAN database is mainly used by readers in data path, and rarely >> used by control path writers. >> Multiple readers (threads) should not blo

Re: [net-next 04/13] net/mlx5e: Vxlan, replace spinlock with read-write lock

2018-07-27 Thread Stephen Hemminger
On Fri, 27 Jul 2018 14:15:09 -0700 Saeed Mahameed wrote: > From: Gal Pressman > > The VXLAN database is mainly used by readers in data path, and rarely > used by control path writers. > Multiple readers (threads) should not block each other and cause an > unnecessary contention on the lock. >

[net-next 04/13] net/mlx5e: Vxlan, replace spinlock with read-write lock

2018-07-27 Thread Saeed Mahameed
From: Gal Pressman The VXLAN database is mainly used by readers in data path, and rarely used by control path writers. Multiple readers (threads) should not block each other and cause an unnecessary contention on the lock. Replacing the spinlock with rwlock optimizes the common use case where ad