public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Matthias Schiffer <mschiffer@universe-factory.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] The current state of the batman-adv vis code
Date: Wed, 09 May 2012 16:59:00 +0200	[thread overview]
Message-ID: <4FAA8634.7070809@universe-factory.net> (raw)
In-Reply-To: <201205091904.27376.lindner_marek@yahoo.de>

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

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 :)

Matthias


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2012-05-09 14:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-07 19:35 [B.A.T.M.A.N.] The current state of the batman-adv vis code Matthias Schiffer
2012-05-08  5:59 ` Marek Lindner
2012-05-08 14:18   ` Matthias Schiffer
2012-05-09 11:04     ` Marek Lindner
2012-05-09 14:59       ` Matthias Schiffer [this message]
2012-05-10 13:16         ` Marek Lindner
2012-05-08 20:31   ` [B.A.T.M.A.N.] [PATCH] batman-adv: fix locking in hash_add() Matthias Schiffer
2012-05-08 20:38     ` Sven Eckelmann
2012-05-11 19:50       ` Marek Lindner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FAA8634.7070809@universe-factory.net \
    --to=mschiffer@universe-factory.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox