[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221123142817.2094993-1-nikolay.borisov@virtuozzo.com>
Date: Wed, 23 Nov 2022 16:28:14 +0200
From: Nikolay Borisov <nikolay.borisov@...tuozzo.com>
To: nhorman@...driver.com
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
netdev@...r.kernel.org, kernel@...tuozzo.com,
Nikolay Borisov <nikolay.borisov@...tuozzo.com>
Subject: [PATCH net-next v2 0/3] Add support for netnamespace filtering in drop monitor
This series adds support for conveying as well as filtering based on the the
id of the net namespace where a particular event originated. This is especially
useful when dealing with systems hosting 10s or 100s of containers.
Currently software as well as devlink-originated drops are supported. The output
would look like the following:
11 drops at location 0xffffffffad8cd0c3 [software] [ns: 4026532485]
11 drops at location 0xffffffffad8cd0c3 [software] [ns: 4026532513]
Changes in v2:
* Fixed the inadvertent uapi breakage by appending the newly added netlink
attributes. All tests are now passing.
Nikolay Borisov (3):
drop_monitor: Implement namespace filtering/reporting for software
drops
drop_monitor: Add namespace filtering/reporting for hardware drops
selftests: net: Add drop monitor tests for namespace filtering
functionality
include/uapi/linux/net_dropmon.h | 3 +
net/core/drop_monitor.c | 64 ++++++++-
.../selftests/net/drop_monitor_tests.sh | 127 +++++++++++++++---
3 files changed, 171 insertions(+), 23 deletions(-)
--
2.34.1
Powered by blists - more mailing lists