Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752940AbbLRGUv (ORCPT ); Fri, 18 Dec 2015 01:20:51 -0500 Received: from mail-pa0-f42.google.com ([209.85.220.42]:35333 "EHLO mail-pa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752447AbbLRGUt (ORCPT ); Fri, 18 Dec 2015 01:20:49 -0500 Date: Thu, 17 Dec 2015 22:20:44 -0800 From: Alexei Starovoitov To: Ming Lei Cc: Yang Shi , Linux Kernel Mailing List , Alexei Starovoitov , "David S. Miller" , Network Development , Steven Rostedt Subject: Re: [PATCH 4/6] bpf: hash: convert per-hashtable lock into per-bucket bit spinlock Message-ID: <20151218062043.GB59584@ast-mbp.thefacebook.com> References: <1450178464-27721-1-git-send-email-tom.leiming@gmail.com> <1450178464-27721-5-git-send-email-tom.leiming@gmail.com> <20151215225118.GA67370@ast-mbp.thefacebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 963 Lines: 24 On Wed, Dec 16, 2015 at 02:58:08PM +0800, Ming Lei wrote: > On Wed, Dec 16, 2015 at 1:01 PM, Yang Shi wrote: > > > > > I recalled Steven confirmed raw_spin_lock has the lockdep benefit too in the > > patch review for changing to raw lock. > > > > Please check this thread out > > http://lists.openwall.net/netdev/2015/10/31/7 > > OK, looks I was wrong about the lockdep benifit, :-( > > But for this lock, I think lockdep isn't such important, because it is the > intermost lock, and it can be used just for protecting the bucket list > and nothing else need to be covered. I still think that overhead of normal spinlock per bucket is acceptable. Makes the whole thing much easier to read. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/