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: [B.A.T.M.A.N.] batman-adv 2011.1.0 released
Date: Tue, 19 Apr 2011 13:45:35 +0200 [thread overview]
Message-ID: <201104191345.36184.lindner_marek@yahoo.de> (raw)
The B.A.T.M.A.N. team is publishing its second 2011 release - 2011.1.0,
containing major code changes under the hood to improve performance and
scalability plus the usual set of bug fixes. As the kernel module always
depends on the Linux kernel it was compiled against, it does not make sense to
provide binaries on our website. As usual, you will find the signed tarballs
in our download section:
http://downloads.open-mesh.org/batman/releases/batman-adv-2011.1.0/
as well as prepackaged binaries in your distribution.
Thanks
------
Thanks to all people sending in patches:
* Jesper Juhl <jj@chaosbits.net>
* Linus Lüssing <linus.luessing@web.de>
* Lucas De Marchi <lucas.demarchi@profusion.mobi>
* Marek Lindner <lindner_marek@yahoo.de>
* Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
* Sven Eckelmann <sven@narfation.org>
* Sylvestre Ledru <sylvestre.ledru@scilab.org>
batman-adv
----------
The principal objective while working towards this release was to remove the
originator hash lock (also known as the batman-adv private "big kernel lock").
It was introduced in the very early stages of the batman-adv development which
proved to be a simple and effective way to protect all originator node
information from parallel access. As time went on, the module grew and gained
more features - most of them making heavy use of the aforementioned originator
hash lock as it safeguarded the module's central pool of data. It thereby
became a major bottleneck because almost every piece of code had to acquire
this very same lock. An extensive effort was necessary to replace the
originator hash lock by fine grained locking which only locks the bare minimum
of data to improve the module's performance and scalability.
Other parts of the code received attention too: After learning about
bufferbloat in one of Jim Getty's talks we revisited our own buffering
settings and decided to set the txqueuelen to zero. Fragmented packets are now
properly linearized upon receipt to avoid a crash if the network card splits
the packet into smaller chunks. The fragment numbering became more robust and
several spelling mistakes have been corrected.
batctl
------
To render batctl more versatile packet dump functionality support for raw WiFi
packet decapsulation was added. This allows to keep an eye on your network
using interfaces in monitor mode which output packets including all WiFi
headers. The bug causing to display an erroneously warning message when
changing gateway settings has been squashed. Unused code and the last trace of
our subversion integration in the Makefile have been removed.
Happy routing,
The B.A.T.M.A.N. team
next reply other threads:[~2011-04-19 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 11:45 Marek Lindner [this message]
2011-04-20 22:07 ` [B.A.T.M.A.N.] batman-adv 2011.1.0 released Gioacchino Mazzurco
2011-04-20 22:42 ` Marek Lindner
2011-04-20 22:44 ` Gioacchino Mazzurco
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=201104191345.36184.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox