[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190811.115718.938803082109468275.davem@davemloft.net>
Date: Sun, 11 Aug 2019 11:57:18 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: idosch@...sch.org
Cc: netdev@...r.kernel.org, nhorman@...driver.com, jiri@...lanox.com,
toke@...hat.com, dsahern@...il.com, roopa@...ulusnetworks.com,
nikolay@...ulusnetworks.com, jakub.kicinski@...ronome.com,
andy@...yhouse.net, f.fainelli@...il.com, andrew@...n.ch,
vivien.didelot@...il.com, mlxsw@...lanox.com, idosch@...lanox.com
Subject: Re: [PATCH net-next v2 00/10] drop_monitor: Capture dropped
packets and metadata
From: Ido Schimmel <idosch@...sch.org>
Date: Sun, 11 Aug 2019 10:35:45 +0300
> From: Ido Schimmel <idosch@...lanox.com>
>
> So far drop monitor supported only one mode of operation in which a
> summary of recent packet drops is periodically sent to user space as a
> netlink event. The event only includes the drop location (program
> counter) and number of drops in the last interval.
>
> While this mode of operation allows one to understand if the system is
> dropping packets, it is not sufficient if a more detailed analysis is
> required. Both the packet itself and related metadata are missing.
>
> This patchset extends drop monitor with another mode of operation where
> the packet - potentially truncated - and metadata (e.g., drop location,
> timestamp, netdev) are sent to user space as a netlink event. Thanks to
> the extensible nature of netlink, more metadata can be added in the
> future.
...
Series applied.
Powered by blists - more mailing lists