On Thursday, September 08, 2011 18:40:44 Marek Lindner wrote:
here comes the next batch batch I'd like to get the pulled into net-next-2.6/3.2. These patches mainly focus restructering the routing code in order to allow the kernel module the handling of the current routing algorithm and the upcoming one.
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 ?
Note: The new algorithm has been designed with backward compatibility in mind (using TLVs). We are trying to address the incompatibility issue you and others have pointed out.
Forgot to mention: We are well aware of the difficulties after the kernel.org intrusion. If you can't pull our patches right now, feel free to do it whenever kernel.org is back online.
Regards, Marek