[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ygnhwnzc6ft5.fsf@nvidia.com>
Date: Mon, 26 Oct 2020 19:46:30 +0200
From: Vlad Buslov <vladbu@...dia.com>
To: Jamal Hadi Salim <jhs@...atatu.com>
CC: Vlad Buslov <vlad@...lov.dev>, <dsahern@...il.com>,
<stephen@...workplumber.org>, <netdev@...r.kernel.org>,
<davem@...emloft.net>, <xiyou.wangcong@...il.com>,
<jiri@...nulli.us>, <ivecera@...hat.com>,
Vlad Buslov <vladbu@...lanox.com>
Subject: Re: [PATCH iproute2-next v3 2/2] tc: implement support for terse dump
On Mon 26 Oct 2020 at 19:12, Jamal Hadi Salim <jhs@...atatu.com> wrote:
> On 2020-10-26 7:28 a.m., Vlad Buslov wrote:
>>
>> On Sat 24 Oct 2020 at 20:40, Jamal Hadi Salim <jhs@...atatu.com> wrote:
>
> [..]
>>>>
>>>> Yes, that makes sense. I guess introducing something like 'tc action -br
>>>> ls ..' mode implemented by means of existing terse flag + new 'also
>>>> output action index' flag would achieve that goal.
>>>>
>>>
>>> Right. There should be no interest in the cookie here at all. Maybe
>>> it could be optional with a flag indication.
>>> Have time to cook a patch? I'll taste/test it.
>>
>> Patch to make cookie in filter terse dump optional? That would break
>> existing terse dump users that rely on it (OVS).
>
> Meant patch for 'tc action -br ls'
>
> Which by default would not include the cookie.
So action-dump-specific flag that causes act api to output action index
(via new attribute) and skips cookie?
>
> cheers,
> jamal
Powered by blists - more mailing lists