netdev - Re: [ovs-dev] OVS Offload Decision Proposal

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: <20150305.142157.803216605925013984.davem@davemloft.net>
Date:	Thu, 05 Mar 2015 14:21:57 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	marichika4@...il.com
Cc:	john.fastabend@...il.com, jhs@...atatu.com, therbert@...gle.com,
	davidch@...adcom.com, simon.horman@...ronome.com,
	dev@...nvswitch.org, netdev@...r.kernel.org, pablo@...filter.org
Subject: Re: [ovs-dev] OVS Offload Decision Proposal

I find it funny that we haven't even got a L3 forwarding
implementation fleshed out enough to merge into the tree, and people
are talking about VOIP to VLAN classification, hw bug workarounds, and
shit like that.

Everyone is really jumping the gun on all of this.

Nobody knows what we will need, and I do mean nobody.  Not me, not
switch hardware guys, not people working on the code actively right
now.  Nobody.

The only way to find out is to _do_, in small incremental steps,
rather than big revolutionary changes.

Simplify, consolidate, and optimize later.

Let's get something that works for at least the simplest cases first.
We don't even have that yet.

So if people could drive their attention towards Scott's L3 forwarding
work instead of this flow crap which is too far into the horizon to
even be properly seen yet, I'd _really_ appreciate it.

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