From: Vlad Buslov <vlad@buslov.dev>
To: David Ahern <dsahern@gmail.com>
Cc: Vlad Buslov <vladbu@nvidia.com>,
stephen@networkplumber.org, netdev@vger.kernel.org,
Vlad Buslov <vladbu@mellanox.com>, Jiri Pirko <jiri@mellanox.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>
Subject: Re: [RESEND PATCH iproute2-next 2/2] tc: implement support for terse dump
Date: Wed, 30 Sep 2020 20:02:31 +0300 [thread overview]
Message-ID: <87tuvf6vvc.fsf@buslov.dev> (raw)
In-Reply-To: <0d4e9eb2-ab6b-432c-9185-c93bbf927d1f@gmail.com>
On Wed 30 Sep 2020 at 18:57, David Ahern <dsahern@gmail.com> wrote:
> On 9/30/20 12:36 AM, Vlad Buslov wrote:
>> From: Vlad Buslov <vladbu@mellanox.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:
>>
>>> tc -s filter show terse dev ens1f0 ingress
>
> this should be consistent with ip command which has -br for 'brief'
> output. so this should be
>
> tc -s -br filter show dev ens1f0 ingress
>
> Other tc maintainers should weigh in on what data should be presented
> for this mode.
Thanks for the feedback, David! I've just sent V2 with -br option.
[...]
next prev parent reply other threads:[~2020-09-30 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 7:36 [RESEND PATCH iproute2-next 0/2] Implement filter terse dump mode support Vlad Buslov
2020-09-30 7:36 ` [RESEND PATCH iproute2-next 1/2] tc: skip actions that don't have options attribute when printing Vlad Buslov
2020-09-30 7:36 ` [RESEND PATCH iproute2-next 2/2] tc: implement support for terse dump Vlad Buslov
2020-09-30 15:57 ` David Ahern
2020-09-30 17:02 ` Vlad Buslov [this message]
2020-09-30 17:33 ` Stephen Hemminger
2020-09-30 20:11 ` Vlad Buslov
2020-09-30 11:31 ` [RESEND PATCH iproute2-next 0/2] Implement filter terse dump mode support Ivan Vecera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tuvf6vvc.fsf@buslov.dev \
--to=vlad@buslov.dev \
--cc=dsahern@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vladbu@mellanox.com \
--cc=vladbu@nvidia.com \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.