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: Mon, 30 Jul 2018 17:38:43 -0700 From: Jakub Kicinski <kubakici@...pl> To: Jiri Pirko <jiri@...nulli.us> Cc: Michal Kubecek <mkubecek@...e.cz>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, David Miller <davem@...emloft.net>, Florian Fainelli <f.fainelli@...il.com>, Roopa Prabhu <roopa@...ulusnetworks.com>, "John W. Linville" <linville@...driver.com> Subject: Re: [RFC PATCH net-next v2 00/17] ethtool netlink interface (WiP) On Mon, 30 Jul 2018 15:07:47 +0200, Jiri Pirko wrote: > >- find reasonable format for data transfers (e.g. eeprom dump or flash); > > I don't have clear idea how big these can get and if 64 KB limit on > > attribute size (including nested ones) is a problem; if so, dumps can > > be an answer for dumps, some kind of multi-message requests would be > > needed for flashes > > This is another thing that should go into devlink as it is not > netdev-handled. We have now a "region" facility there which can be > re-used. +1 regions should cover the current use cases and are a better API IMHO.
Powered by blists - more mailing lists