netdev - Re: [RFC PATCH net-next v2 0/1] Add support of ECMPv6

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 15 Oct 2012 21:54:48 +0200
From:	Vincent Bernat <bernat@...fy.cx>
To:	<nicolas.dichtel@...nd.com>
Cc:	<yoshfuji@...ux-ipv6.org>, <netdev@...r.kernel.org>,
	<davem@...emloft.net>
Subject: Re: [RFC PATCH net-next v2 0/1] Add support of ECMPv6

 ❦ 15 octobre 2012 14:36 CEST, Vincent Bernat <bernat@...fy.cx> :

> The problem is the same with BIRD. The difference with IPv4 makes it
> difficult to factor the code between IPv4 and IPv6. What do you think?

I am in the process of creating the appropriate patches for Quagga and
it is less difficult that I thought. It is possible to plug the
difference between IPv4 and IPv6 for multipath routes right into the
difference between IPv4 single hop and IPv4 multi hop routes that are
also handled differently.

I am still thinking that the approach is confusing for the userland but
it is not really cumbersome from the implementor point of view and it
has also some advantages.
-- 
Make it clear before you make it faster.
            - The Elements of Programming Style (Kernighan & Plauger)
--
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