| 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
| ||
|
Date: Thu, 09 Apr 2015 17:34:23 -0400 (EDT) From: David Miller <davem@...emloft.net> To: jiri@...nulli.us Cc: netdev@...r.kernel.org, jhs@...atatu.com, tgraf@...g.ch, jesse@...ira.com Subject: Re: [patch net-next v3] tc: introduce OpenFlow classifier From: Jiri Pirko <jiri@...nulli.us> Date: Thu, 9 Apr 2015 14:58:07 +0200 > This patch introduces OpenFlow-based filter. So far, the very essential > packet fields are supported (according to OpenFlow v1.4 spec). > > This patch is only the first step. There is a lot of potential performance > improvements possible to implement. Also a lot of features are missing > now. They will be addressed in follow-up patches. > > To the name of this classifier, I believe that "cls_openflow" is pretty > accurate. It is actually a OpenFlow classifier. > > Signed-off-by: Jiri Pirko <jiri@...nulli.us> I'm not so sure what my opinion is about whether we should even have an openflow classifier or not (I find major aspects of OpenFLOW extremely distasteful, it's basically pushing the SDK agenda of several major chip vendors). However I am sure that I majorly object to having yet another flow parsing engine. Therefore, at least adjust this code to use our flow dissector and datastructures. Adjust the flow dissector to fit your needs, if necessary. -- 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
Powered by blists - more mailing lists