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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 7 Oct 2020 18:40:22 -0700 From: David Ahern <dsahern@...il.com> To: Vlad Buslov <vladbu@...dia.com>, stephen@...workplumber.org, jhs@...atatu.com, xiyou.wangcong@...il.com Cc: netdev@...r.kernel.org, davem@...emloft.net, jiri@...nulli.us, ivecera@...hat.com, Vlad Buslov <vladbu@...lanox.com> Subject: Re: [PATCH iproute2-next v2 2/2] tc: implement support for terse dump On 9/30/20 9:59 AM, Vlad Buslov wrote: > From: Vlad Buslov <vladbu@...lanox.com> > > Implement support for classifier/action terse dump using new TCA_DUMP_FLAGS > tlv with only available flag value TCA_DUMP_FLAGS_TERSE. Set the flag when > user requested it with following example CLI (-br for 'brief'): > >> tc -s -br filter show dev ens1f0 ingress > > In terse mode dump only outputs essential data needed to identify the > filter and action (handle, cookie, etc.) and stats, if requested by the > user. The intention is to significantly improve rule dump rate by omitting > all static data that do not change after rule is created. > I really want to get agreement from other heavy tc users about what the right information is for a brief mode.
Powered by blists - more mailing lists