[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201023112027.74ae41d1@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date: Fri, 23 Oct 2020 11:20:27 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: izabela.bakollari@...il.com
Cc: nhorman@...driver.com, davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
linux-kernel-mentees@...ts.linuxfoundation.org
Subject: Re: [PATCHv4 net-next] dropwatch: Support monitoring of dropped
frames
On Fri, 23 Oct 2020 06:29:43 +0200 izabela.bakollari@...il.com wrote:
> From: Izabela Bakollari <izabela.bakollari@...il.com>
>
> Dropwatch is a utility that monitors dropped frames by having userspace
> record them over the dropwatch protocol over a file. This augument
> allows live monitoring of dropped frames using tools like tcpdump.
>
> With this feature, dropwatch allows two additional commands (start and
> stop interface) which allows the assignment of a net_device to the
> dropwatch protocol. When assinged, dropwatch will clone dropped frames,
> and receive them on the assigned interface, allowing tools like tcpdump
> to monitor for them.
>
> With this feature, create a dummy ethernet interface (ip link add dev
> dummy0 type dummy), assign it to the dropwatch kernel subsystem, by using
> these new commands, and then monitor dropped frames in real time by
> running tcpdump -i dummy0.
>
> Signed-off-by: Izabela Bakollari <izabela.bakollari@...il.com>
Doesn't seem to apply to net-next, also the tree is closed during the
merge window so please rebase and repost after the weekend.
Powered by blists - more mailing lists