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: Wed, 10 Oct 2012 15:28:26 +0100 From: Ben Hutchings <bhutchings@...arflare.com> To: Or Gerlitz <ogerlitz@...lanox.com> CC: Rony Efraim <ronye@...lanox.com>, netdev <netdev@...r.kernel.org>, Amir Vadai <amirv@...lanox.com> Subject: Re: setting flow spec rules under vswitch configuration On Wed, 2012-10-10 at 16:16 +0200, Or Gerlitz wrote: [...] > Thanks for setting the sketch of a plan here... so if we go little bit > into details, we can safely move 20 bytes from the hadata[60] field into > the beginning of struct ethtool_flow_ext, which will still allow old > user space to work with newer kernels. As for newer uses space that > would like to set mac addresses within > ethtool_flow_ext, how are they supposed to identify if the kernel > supports this extension (of the extension...)? Well they can't tell in advance, but we can define another flag in flow_type like FLOW_EXT and existing drivers will reject flow specs with that flag set. > this might be newbee > question, I didn't made many ethtool patches so far. > > Also on a related note, what does the 64bit data field of > ethtool_flow_ext used for? Driver-dependent. ixgbe uses it for something. Ben. -- Ben Hutchings, Staff Engineer, Solarflare Not speaking for my employer; that's the marketing department's job. They asked us to note that Solarflare product names are trademarked. -- 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