[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210125121234.GJ3565223@nanopsycho.orion>
Date: Mon, 25 Jan 2021 13:12:34 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Ido Schimmel <idosch@...sch.org>,
Oleksandr Mazur <oleksandr.mazur@...ision.eu>,
netdev@...r.kernel.org, jiri@...dia.com, davem@...emloft.net,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] net: core: devlink: add new trap action
HARD_DROP
Thu, Jan 21, 2021 at 06:36:05PM CET, kuba@...nel.org wrote:
>On Thu, 21 Jan 2021 14:21:52 +0200 Ido Schimmel wrote:
>> On Thu, Jan 21, 2021 at 01:29:37PM +0200, Oleksandr Mazur wrote:
>> > Add new trap action HARD_DROP, which can be used by the
>> > drivers to register traps, where it's impossible to get
>> > packet reported to the devlink subsystem by the device
>> > driver, because it's impossible to retrieve dropped packet
>> > from the device itself.
>> > In order to use this action, driver must also register
>> > additional devlink operation - callback that is used
>> > to retrieve number of packets that have been dropped by
>> > the device.
>>
>> Are these global statistics about number of packets the hardware dropped
>> for a specific reason or are these per-port statistics?
>>
>> It's a creative use of devlink-trap interface, but I think it makes
>> sense. Better to re-use an existing interface than creating yet another
>> one.
>
>Not sure if I agree, if we can't trap why is it a trap?
>It's just a counter.
+1
Powered by blists - more mailing lists