From: Marek Lindner <lindner_marek@yahoo.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.] [PATCH] batman-adv: Use successive sequence numbers for fragments
Date: Thu, 10 Feb 2011 15:32:34 +0100 [thread overview]
Message-ID: <201102101532.34780.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1297208102-4931-1-git-send-email-sven@narfation.org>
On Wednesday 09 February 2011 00:35:02 Sven Eckelmann wrote:
> The access to the fragment sequence number pool has either to be protected
> by correct locking or the access to the pool has to reserve two sequence
> numbers in a single access. The latter one can easily be done by
> increasing the value of the last used sequence number by 2 in a single
> access. The generated window of two currently unused sequence numbers can
> now be scattered across the two fragments.
Applied in revision 1940.
Thanks,
Marek
prev parent reply other threads:[~2011-02-10 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 23:35 [B.A.T.M.A.N.] [PATCH] batman-adv: Use successive sequence numbers for fragments Sven Eckelmann
2011-02-10 14:32 ` Marek Lindner [this message]
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=201102101532.34780.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.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.