netdev - Re: MPLS for Linux kernel

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: <4ECAA41C.9040007@dti2.net>
Date:	Mon, 21 Nov 2011 20:18:52 +0100
From:	"Jorge Boncompte [DTI2]" <jorge@...2.net>
To:	davem@...emloft.net
CC:	igorm@....rs, netdev@...r.kernel.org
Subject: Re: MPLS for Linux kernel

El 21/11/2011 19:29, David Miller escribió:
> From: "Jorge Boncompte [DTI2]" <jorge@...2.net>
> Date: Mon, 21 Nov 2011 16:01:26 +0100
> 
>> 	mpls-linux it is not ready to go upstream in my opinion.
> 
> And can arguably be implemented in terms of openvswitch and packet scheduler actions.

	I guess so, I have not really looked much at the openvswitch code. The MPLS
code it is pretty self contained and in my opinion more tied to routing than to
switching (*). I don't think it should be necessary an userspace daemon, like it
seems necessary for openvswitch, just to bind a label to a route, the same way
that it is not necessary a daemon to support VLAN's currently. The label
signaling protocols are already complicated :)

	I work in this code, like a lot of people do, because I have a use for it. I
would really like to see it upstreamed but if it does not fit upstream plans, it
is not a problem, this code it is not that hard to maintain.

	In any case critics/reviews/patches are most than welcome.

(*) The code that you implemented for 2.6.1 and that James R. Leu used in this
codebase it is even more tied together to routing.

--
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