This is not really a series, as the commits will be delivered one by one. I think I have got as far as I can with this one now; it feels pretty solid even when I push the envelope to 500 namespaces.
v6: - Added the jiffies-to-ms patch as #1. Please ack asap, since net-next is still open. - Updated monitor patch to v6. See commit log. It is starting to look pretty stable now. - Separated out the disovery rate control as commit #3. - More measuring points in the profiling commit (#4) v7: - Added a new commit #1, which solves a problem I have been chasing for some time. - Updated #3 (v6/#2), see its commit log. - Removed v6/#3 as it doesn't seem to make any difference. - Finally got the "monitored links" counter in #4 right, plus more. Jon Maloy (4): tipc: correct error in node fsm tipc: change node timer unit from jiffies to ms tipc: add neighbor monitoring framework tipc: debugging_tracing_profiling support for neighbor monitoring code net/tipc/Makefile | 2 +- net/tipc/addr.c | 1 + net/tipc/addr.h | 1 + net/tipc/bearer.c | 18 +- net/tipc/bearer.h | 2 +- net/tipc/core.c | 1 + net/tipc/core.h | 15 +- net/tipc/link.c | 90 +++- net/tipc/monitor.c | 1244 ++++++++++++++++++++++++++++++++++++++++++++++++++++ net/tipc/monitor.h | 226 ++++++++++ net/tipc/msg.c | 32 +- net/tipc/node.c | 65 +-- 12 files changed, 1634 insertions(+), 63 deletions(-) create mode 100644 net/tipc/monitor.c create mode 100644 net/tipc/monitor.h -- 1.9.1 ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ tipc-discussion mailing list tipc-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tipc-discussion