From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH next-net] ipv6: Use hlist_for_each_entry_rcu_bh() in ipv6_chk_same_addr() Date: Tue, 01 Nov 2011 05:06:36 -0400 (EDT) Message-ID: <20111101.050636.2188753893784711943.davem@davemloft.net> References: <20111101.043938.1065811675133329291.davem@davemloft.net> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: roy.qing.li@gmail.com Return-path: Received: from shards.monkeyblade.net ([198.137.202.13]:34681 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752231Ab1KAJGj (ORCPT ); Tue, 1 Nov 2011 05:06:39 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: From: RongQing Li Date: Tue, 1 Nov 2011 17:05:19 +0800 > 2011/11/1 David Miller : >> From: RongQing Li >> Date: Tue, 1 Nov 2011 16:33:49 +0800 >> >>> Yes, But I think the code readable is not good, >> >> It is wasteful to add multiple BH disables and RCU memory >> barriers in code paths where it is not necessary. >> >> Your patch fixes no real bug, and adds a regression. >> > > hlist_for_each_entry_rcu_bh() does not disable BH, > it only check If BH is disabled. > > These codes is different from normal RCU convention. But adding _rcu does add memory barriers.