Thread (1 message) 1 message, 1 author, 2011-11-23

Re: [PATCH net-next 4/4] net: Add Open vSwitch kernel components.

From: David Miller <hidden>
Date: 2011-11-23 01:42:03

From: Jesse Gross <redacted>
Date: Tue, 22 Nov 2011 17:34:57 -0800
On Tue, Nov 22, 2011 at 3:19 PM, David Miller [off-list ref] wrote:
quoted
From: Jesse Gross <redacted>
Date: Tue, 22 Nov 2011 15:11:33 -0800
quoted
As you mention, one of the biggest benefits of Open vSwitch is how
simple the kernel portions are (it's less than 6000 lines).  It's
existed as an out-of-tree project for several years now so it's
actually fairly mature already and unlikely that there will be a
sudden influx of new code over the coming months.
The packet scheduler classification and packet action infrastructure
has been around 5 times longer.
The only point that I was trying to make with that comment is that
it's unlikely that Open vSwitch will suddenly get more complex due to
the introduction of new code.
And it will get instantly less complex if it uses existing
infrastructure.

There is no reasonable argument against using what we have already.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help