From: Ivan Vecera <ivecera@redhat.com>
To: Vlad Buslov <vladbu@nvidia.com>
Cc: dsahern@gmail.com, stephen@networkplumber.org, netdev@vger.kernel.org
Subject: Re: [RESEND PATCH iproute2-next 0/2] Implement filter terse dump mode support
Date: Wed, 30 Sep 2020 13:31:45 +0200 [thread overview]
Message-ID: <20200930133145.373cb94d@ceranb> (raw)
In-Reply-To: <20200930073651.31247-1-vladbu@nvidia.com>
On Wed, 30 Sep 2020 10:36:49 +0300
Vlad Buslov <vladbu@nvidia.com> wrote:
> Implement support for terse dump mode which provides only essential
> classifier/action info (handle, stats, cookie, etc.). Use new
> TCA_DUMP_FLAGS_TERSE flag to prevent copying of unnecessary data from
> kernel.
>
> Vlad Buslov (2):
> tc: skip actions that don't have options attribute when printing
> tc: implement support for terse dump
>
> tc/m_bpf.c | 2 +-
> tc/m_connmark.c | 2 +-
> tc/m_csum.c | 2 +-
> tc/m_ct.c | 2 +-
> tc/m_ctinfo.c | 2 +-
> tc/m_gact.c | 2 +-
> tc/m_ife.c | 2 +-
> tc/m_ipt.c | 2 +-
> tc/m_mirred.c | 2 +-
> tc/m_mpls.c | 2 +-
> tc/m_nat.c | 2 +-
> tc/m_pedit.c | 2 +-
> tc/m_sample.c | 2 +-
> tc/m_simple.c | 2 +-
> tc/m_skbedit.c | 2 +-
> tc/m_skbmod.c | 2 +-
> tc/m_tunnel_key.c | 2 +-
> tc/m_vlan.c | 2 +-
> tc/m_xt.c | 2 +-
> tc/m_xt_old.c | 2 +-
> tc/tc_filter.c | 12 ++++++++++++
> 21 files changed, 32 insertions(+), 20 deletions(-)
>
Tested-by: Ivan Vecera <ivecera@redhat.com>
prev parent reply other threads:[~2020-09-30 11:31 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
2020-09-30 17:33 ` Stephen Hemminger
2020-09-30 20:11 ` Vlad Buslov
2020-09-30 11:31 ` Ivan Vecera [this message]
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=20200930133145.373cb94d@ceranb \
--to=ivecera@redhat.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vladbu@nvidia.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.