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

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]

Date:	Tue, 22 Nov 2011 20:42:03 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	jesse@...ira.com
Cc:	jhs@...atatu.com, netdev@...r.kernel.org, dev@...nvswitch.org
Subject: Re: [PATCH net-next 4/4] net: Add Open vSwitch kernel components.

From: Jesse Gross <jesse@...ira.com>
Date: Tue, 22 Nov 2011 17:34:57 -0800

> On Tue, Nov 22, 2011 at 3:19 PM, David Miller <davem@...emloft.net> wrote:
>> From: Jesse Gross <jesse@...ira.com>
>> Date: Tue, 22 Nov 2011 15:11:33 -0800
>>
>>> 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.
--
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