[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200930.180150.884209577267624386.davem@davemloft.net>
Date: Wed, 30 Sep 2020 18:01:50 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: idosch@...sch.org
Cc: netdev@...r.kernel.org, kuba@...nel.org, nhorman@...driver.com,
jiri@...dia.com, roopa@...dia.com, aroulin@...dia.com,
ayal@...dia.com, masahiroy@...nel.org, mlxsw@...dia.com,
idosch@...dia.com
Subject: Re: [PATCH net-next 0/7] drop_monitor: Convert to use devlink
tracepoint
From: Ido Schimmel <idosch@...sch.org>
Date: Tue, 29 Sep 2020 11:15:49 +0300
> From: Ido Schimmel <idosch@...dia.com>
>
> Drop monitor is able to monitor both software and hardware originated
> drops. Software drops are monitored by having drop monitor register its
> probe on the 'kfree_skb' tracepoint. Hardware originated drops are
> monitored by having devlink call into drop monitor whenever it receives
> a dropped packet from the underlying hardware.
>
> This patch set converts drop monitor to monitor both software and
> hardware originated drops in the same way - by registering its probe on
> the relevant tracepoint.
>
> In addition to drop monitor being more consistent, it is now also
> possible to build drop monitor as module instead of as a builtin and
> still monitor hardware originated drops. Initially, CONFIG_NET_DEVLINK
> implied CONFIG_NET_DROP_MONITOR, but after commit def2fbffe62c
> ("kconfig: allow symbols implied by y to become m") we can have
> CONFIG_NET_DEVLINK=y and CONFIG_NET_DROP_MONITOR=m and hardware
> originated drops will not be monitored.
...
Series applied, thank you.
Powered by blists - more mailing lists