netdev - openvswitch/flow WAS ( Re: [rfc] Merging the Open vSwitch datapath

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: <1287142292.3642.19.camel@bigi>
Date:	Fri, 15 Oct 2010 07:31:32 -0400
From:	jamal <hadi@...erus.ca>
To:	Ben Pfaff <blp@...ira.com>, Jesse Gross <jesse@...ira.com>
Cc:	netdev@...r.kernel.org
Subject: openvswitch/flow WAS ( Re: [rfc] Merging the Open vSwitch datapath

Sorry, slightly off topic - and this old (catching up 
with netdev randomly going backwards)..

I was curious after seeing the exchange with Eric D. on
the tunnels and how you have your own tree so i glossed 
over what your project is doing.

It seems to me that you reinvented things that exist in 
Linux already such as bridging, tunnels and what really
caught my attention: ability to do flows (tc actions).
It is possible Linux is missing something you wanted or was
not efficient enough? 
[For example: I couldnt see anything you needed
on flow-action management that Linux couldnt do already
(with already very nice well structured netlink APIs)]

cheers,
jamal

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