[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190806131956.26168-1-idosch@idosch.org>
Date: Tue, 6 Aug 2019 16:19:50 +0300
From: Ido Schimmel <idosch@...sch.org>
To: netdev@...r.kernel.org
Cc: davem@...emloft.net, nhorman@...driver.com, toke@...hat.com,
jiri@...lanox.com, dsahern@...il.com, mlxsw@...lanox.com,
Ido Schimmel <idosch@...lanox.com>
Subject: [PATCH net-next 0/6] drop_monitor: Various improvements and cleanups
From: Ido Schimmel <idosch@...lanox.com>
This patchset performs various improvements and cleanups in drop monitor
with no functional changes intended. There are no changes in these
patches relative to the RFC I sent two weeks ago [1].
A followup patchset will extend drop monitor with a packet alert mode in
which the dropped packet is notified to user space instead of just a
summary of recent drops. Subsequent patchsets will add the ability to
monitor hardware originated drops via drop monitor.
[1] https://patchwork.ozlabs.org/cover/1135226/
Ido Schimmel (6):
drop_monitor: Use correct error code
drop_monitor: Rename and document scope of mutex
drop_monitor: Document scope of spinlock
drop_monitor: Avoid multiple blank lines
drop_monitor: Add extack support
drop_monitor: Use pre_doit / post_doit hooks
net/core/drop_monitor.c | 58 +++++++++++++++++++++++++++--------------
1 file changed, 38 insertions(+), 20 deletions(-)
--
2.21.0
Powered by blists - more mailing lists