Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933749AbbLPG6M (ORCPT ); Wed, 16 Dec 2015 01:58:12 -0500 Received: from mail-wm0-f44.google.com ([74.125.82.44]:38361 "EHLO mail-wm0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932197AbbLPG6K (ORCPT ); Wed, 16 Dec 2015 01:58:10 -0500 MIME-Version: 1.0 In-Reply-To: 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> Date: Wed, 16 Dec 2015 14:58:08 +0800 Message-ID: Subject: Re: [PATCH 4/6] bpf: hash: convert per-hashtable lock into per-bucket bit spinlock From: Ming Lei To: Yang Shi Cc: Alexei Starovoitov , Linux Kernel Mailing List , Alexei Starovoitov , "David S. Miller" , Network Development , Steven Rostedt Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 778 Lines: 23 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. Thanks, Ming Lei -- 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/