From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
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.] [RFC] batman-adv: postpone OGM preparation to sending time
Date: Tue, 11 Dec 2012 23:34:35 +0100 [thread overview]
Message-ID: <20121211223435.GA17765@pandem0nium> (raw)
In-Reply-To: <1355263044-13131-1-git-send-email-ordex@autistici.org>
[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]
On Tue, Dec 11, 2012 at 10:57:24PM +0100, Antonio Quartulli wrote:
> OGMs are currently prepared 1 originator interval in advance then the time they
> are used to be sent. This means that once in the air they carry old information
> (e.g. TT announcements).
>
> To fix this, postpone the OGM creation to the same time of sending, in this way
> the OGM is first created and then immediately sent.
>
> This patch also removes an insane "-2" that was introduced with
> 4d30670880c84071dba4b220f595e64d6c01d1ba ("batman-adv: accept delayed
> rebroadcasts to avoid bogus routing under heavy load") in the OGM seqno
> validation code that was put there to fix a possible heavy loaded scenario.
> First that operation shown to be completely not valid and consequently it was
> creating problem to the new behaviour introduced by this patch
Actually the -2 was not introduced there but was present (in some form) for a much
longer time ... something before 2009, didn't trace it to the very end. :)
The reason for this was:
* seqno is increased right after scheduling a new (own OGM)
* the scheduled OGM was waiting one more cycle before beeing finally sent
Seems we forgot to document this properly, but removing this one is a good idea. :)
Your patch thankfully seems to correctly eliminate both reasons for "correcting" the
incoming seqno.
I haven't reviewed the rest (don't know if this will stir trouble for the aggregation),
but wanted to comment on this history bit. :) Please remove/correct the reference if
you merge or send it again.
Thanks!
Simon
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-12-11 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 21:57 [B.A.T.M.A.N.] [RFC] batman-adv: postpone OGM preparation to sending time Antonio Quartulli
2012-12-11 22:34 ` Simon Wunderlich [this message]
2012-12-13 18:04 ` Antonio Quartulli
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=20121211223435.GA17765@pandem0nium \
--to=simon.wunderlich@s2003.tu-chemnitz.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.