From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Thu, 10 May 2012 21:16:47 +0800 References: <4FA823EB.7070309@universe-factory.net> <201205091904.27376.lindner_marek@yahoo.de> <4FAA8634.7070809@universe-factory.net> In-Reply-To: <4FAA8634.7070809@universe-factory.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201205102116.47554.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] The current state of the batman-adv vis code 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 Wednesday, May 09, 2012 22:59:00 Matthias Schiffer wrote: > On 05/09/2012 01:04 PM, Marek Lindner wrote: > > On Tuesday, May 08, 2012 22:18:34 Matthias Schiffer wrote: > > How the rcu replace / update mechanism works is pretty clear to me. My > > question geared towards our own code base. At which point would you use > > this rcu update ? Every time an element in the hash is modified ? > > Yes, my idea is to use this whenever a new packet is inserted into the > vis hash to ensure the vis data a reader sees is always as consistant as > possible. I know it wouldn't be fatal for the vis if a packet is missing > from the data sometimes, but in my opinion a clean update is nicer :) Feel free to propose patches to introduce this functionality. So far, we have been living without it but maybe we overlooked a potential side effect ? Regards, Marek