From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Thu, 10 Feb 2011 15:25:20 +0100 References: <201102031802.52134.lindner_marek@yahoo.de> <201102081418.38151.lindner_marek@yahoo.de> <20110210104250.GA13038@Sellars> In-Reply-To: <20110210104250.GA13038@Sellars> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201102101525.21265.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] [PATCH 5/7] batman-adv: Make bat_priv->curr_gw an rcu protected pointer Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking On Thursday 10 February 2011 11:42:50 Linus L=C3=BCssing wrote: > > Would speak anything against re-using the gw_list_lock ? >=20 > ... as we are usually changing the gw_list more often than the > curr_gw, so it's not really necessary to let a gw_list change for > another node wait for a curr_gw_node reassignment to finish. Well, we only need the list lock when we are adding/deleting items from the= =20 list which does not happen that often nor is it time critical. > What is speaking for using the same lock for both, just having > less spinlocks in total in the code? Yes. Regards, Marek