From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Paul E. McKenney" Subject: Re: [PATCH 2/5] rhashtable: don't hold lock on first table throughout insertion. Date: Thu, 26 Jul 2018 20:18:15 -0700 Message-ID: <20180727031815.GW24813@linux.vnet.ibm.com> References: <20180720144152.GW12945@linux.vnet.ibm.com> <87muulqq8q.fsf@notabene.neil.brown.name> <20180722215446.GH12945@linux.vnet.ibm.com> <87h8kqrhi0.fsf@notabene.neil.brown.name> <20180723205625.GZ12945@linux.vnet.ibm.com> <87r2jtpqm4.fsf@notabene.neil.brown.name> <20180724225825.GE12945@linux.vnet.ibm.com> <87in53oqzz.fsf@notabene.neil.brown.name> <20180725152250.GN12945@linux.vnet.ibm.com> <87r2jpmqu2.fsf@notabene.neil.brown.name> Reply-To: paulmck@linux.vnet.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Herbert Xu , Thomas Graf , netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: NeilBrown Return-path: Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:35102 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725821AbeG0EiF (ORCPT ); Fri, 27 Jul 2018 00:38:05 -0400 Received: from pps.filterd (m0098413.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w6R3FZbZ073602 for ; Thu, 26 Jul 2018 23:18:19 -0400 Received: from e12.ny.us.ibm.com (e12.ny.us.ibm.com [129.33.205.202]) by mx0b-001b2d01.pphosted.com with ESMTP id 2kftyb0ukg-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Thu, 26 Jul 2018 23:18:19 -0400 Received: from localhost by e12.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 26 Jul 2018 23:18:18 -0400 Content-Disposition: inline In-Reply-To: <87r2jpmqu2.fsf@notabene.neil.brown.name> Sender: netdev-owner@vger.kernel.org List-ID: On Fri, Jul 27, 2018 at 11:04:37AM +1000, NeilBrown wrote: > On Wed, Jul 25 2018, Paul E. McKenney wrote: > >> > >> Looks good ... except ... naming is hard. > >> > >> is_after_call_rcu_init() asserts where in the lifecycle we are, > >> is_after_call_rcu() tests where in the lifecycle we are. > >> > >> The names are similar but the purpose is quite different. > >> Maybe s/is_after_call_rcu_init/call_rcu_init/ ?? > > > > How about rcu_head_init() and rcu_head_after_call_rcu()? Very well, I will pull this change in on my next rebase. Thanx, Paul