netdev - Re: [B.A.T.M.A.N.] pull request: batman-adv 2011-09-08

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20110921.200539.1422752575190292433.davem@davemloft.net>
Date:	Wed, 21 Sep 2011 20:05:39 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	lindner_marek@...oo.de
Cc:	b.a.t.m.a.n@...ts.open-mesh.org, netdev@...r.kernel.org
Subject: Re: [B.A.T.M.A.N.] pull request: batman-adv 2011-09-08

From: Marek Lindner <lindner_marek@...oo.de>
Date: Thu, 22 Sep 2011 01:39:26 +0200

>  To ensure a smooth transition and efficient testing later, we 
>  decided to offer a choice of routing algorithm but have not     
>  come to a final decision on how to design this choice yet. It
>  either will be a compile time option, a module parameter or a
>  runtime switch. Any suggestions / best practice tips ?

What do you mean by "algorithm"?  Do you mean the implementation
of the data-structure used to perform lookups?

We had two data structures for our main routing table lookup
implementation in ipv4, this was a mistake.  We spent the next couple
years maintaining two pieces of code, and finally investing lots of
effort to eliminate the older code.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html