From: Vlad Buslov <vladbu@nvidia•com>
To: David Ahern <dsahern@gmail•com>
Cc: Jamal Hadi Salim <jhs@mojatatu•com>,
Vlad Buslov <vlad@buslov•dev>, <stephen@networkplumber•org>,
<netdev@vger•kernel.org>, <davem@davemloft•net>,
<xiyou.wangcong@gmail•com>, <jiri@resnulli•us>,
<ivecera@redhat•com>, Vlad Buslov <vladbu@mellanox•com>
Subject: Re: [PATCH iproute2-next v3 2/2] tc: implement support for terse dump
Date: Mon, 26 Oct 2020 17:06:07 +0200 [thread overview]
Message-ID: <ygnhzh4958o0.fsf@nvidia.com> (raw)
In-Reply-To: <0112061b-6890-9f22-bec4-d24a2d67d882@gmail.com>
On Mon 26 Oct 2020 at 16:52, David Ahern <dsahern@gmail•com> wrote:
> On 10/26/20 5:28 AM, Vlad Buslov wrote:
>> Patch to make cookie in filter terse dump optional? That would break
>> existing terse dump users that rely on it (OVS).
>
> Maybe I missed something in the discussions. terse dump for tc has not
> been committed to the tree yet, so there are no users relying on it.
What do you mean? Kernel terse dump flag and implementation have been
committed long time ago and are now present in released kernels.
next prev parent reply other threads:[~2020-10-26 15:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 14:42 [PATCH iproute2-next v3 0/2] Implement filter terse dump mode support Vlad Buslov
2020-10-16 14:42 ` [PATCH iproute2-next v3 1/2] tc: skip actions that don't have options attribute when printing Vlad Buslov
2020-10-16 14:42 ` [PATCH iproute2-next v3 2/2] tc: implement support for terse dump Vlad Buslov
2020-10-16 16:07 ` Jamal Hadi Salim
2020-10-16 16:42 ` Vlad Buslov
2020-10-17 11:20 ` Jamal Hadi Salim
2020-10-18 12:16 ` Vlad Buslov
2020-10-19 13:48 ` Jamal Hadi Salim
2020-10-19 15:18 ` Vlad Buslov
2020-10-20 12:29 ` Jamal Hadi Salim
2020-10-21 8:19 ` Vlad Buslov
2020-10-22 14:05 ` Jamal Hadi Salim
2020-10-23 12:48 ` Vlad Buslov
2020-10-24 17:40 ` Jamal Hadi Salim
2020-10-26 11:28 ` Vlad Buslov
2020-10-26 14:52 ` David Ahern
2020-10-26 15:06 ` Vlad Buslov [this message]
2020-10-26 15:17 ` David Ahern
2020-10-26 17:12 ` Jamal Hadi Salim
2020-10-26 17:46 ` Vlad Buslov
2020-10-26 18:01 ` Jamal Hadi Salim
2020-10-26 18:03 ` Vlad Buslov
2020-10-26 19:56 ` Jamal Hadi Salim
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=ygnhzh4958o0.fsf@nvidia.com \
--to=vladbu@nvidia$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@gmail$(echo .)com \
--cc=ivecera@redhat$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stephen@networkplumber$(echo .)org \
--cc=vlad@buslov$(echo .)dev \
--cc=vladbu@mellanox$(echo .)com \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox