netdev - Re: [GIT PULL v2] Open vSwitch

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: <CAEP_g=-+F8bpkb8Qe1bPk65PQVNxz+VO7NoUrBCw6=GDUFbOFg@mail.gmail.com>
Date:	Tue, 29 Nov 2011 22:18:02 -0800
From:	Jesse Gross <jesse@...ira.com>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	jhs@...atatu.com, David Miller <davem@...emloft.net>,
	netdev@...r.kernel.org, dev@...nvswitch.org
Subject: Re: [GIT PULL v2] Open vSwitch

On Mon, Nov 28, 2011 at 5:04 AM, Herbert Xu <herbert@...dor.apana.org.au> wrote:
> On Wed, Nov 23, 2011 at 07:22:56AM -0500, jamal wrote:
>> I cant find one - you may. After staring at the code, I am also now
>> questioning if the existing bridge code couldnt have been re-used with
>> some small tweaks.
>
> I wasn't able to find any functionality that could not be easily
> done with the existing classifier/action code.
>
> Whether we want to go down this route though is open to debate
> as someone would have to actually implement this :)

Thanks for taking the time to go through the code Herbert.  I think
this conversation overall has suffered some from being a little vague
and high level so it helps a lot to have more people who have looked
at the code.

The main part that worries me about moving to a different approach is
the impedance mismatch that occurs from the fact that Open vSwitch is
modeling a switch and tc is not.  As Jamal alluded to above, it's
actually the bridge code which is more conceptually similar.  In my
experience, combining two disparate models makes things harder over
the long run, not easier.  It also tends to show up more in some of
the edges like userspace/kernel compatibility.

What I'd like to do is start a clean conversation (this one is far too
long already) about what an Open vSwitch built using these components
would look like and really go into the details and design
implications.
--
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