[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHA+R7Md7vGJj_6e8P7iB3j-gaax6H37OQ_9N26KUwjgbWHz_g@mail.gmail.com>
Date: Wed, 27 May 2015 10:44:26 -0700
From: Cong Wang <cwang@...pensource.com>
To: Sorin Dumitru <sorin@...urnze.ro>
Cc: netdev <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Sorin Dumitru <sdumitru@...acom.com>
Subject: Re: [PATCH net-next] vxlan: release lock after each bucket in vxlan_cleanup
On Tue, May 26, 2015 at 12:42 AM, Sorin Dumitru <sorin@...urnze.ro> wrote:
> We're seeing some softlockups from this function when there
> are a lot fdb entries on a vxlan device. Taking the lock for
> each bucket instead of the whole table is enough to fix that.
>
Hmm, then the spinlock could be moved into each bucket, right?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists