lkml.org 
[lkml]   [2019]   [Apr]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH] vxlan: using hash_lock to protect one budegt in vxlan_flush
From
From: Litao Jiao <jiaolitao@raisecom.com>
Date: Thu, 11 Apr 2019 15:06:09 +0800

> The hash_lock will hold long time in vxlan_flush when stopping the
> vxlan device in which there has lots of vxlan fdb entries;it would
> affect the bh process in local cpu; and other cpu would wait for
> a long time in vxlan_snoop until the hash_lock is released;so
> using hash_lock to protect one budegt in vxlan_flush could
> reduce the continuous holding time of the lock.
>
> Signed-off-by: Litao Jiao <jiaolitao@raisecom.com>

Now you are doing FDB_HASH_SIZE spin lock/unlock sequences.

There has to be a better way.

\
 
 \ /
  Last update: 2019-04-12 06:31    [W:0.048 / U:24.520 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site