When running TIPC in large clusters we have experienced behavior
that potentially may become problematic in the future. This series
picks some low-hanging fruit in this regard, and also fixes a
couple of other minor issues.
v2: #1: Found even more remnants to remove.
#2: Clarified problem description, and ensured that even the
first discovery broadcast is sent as it should be.
#3: Introduce a "half" disabling of the bearer to be reset,
and moved the fix to l2 layer code only, where the problem
has manifested itself. We cannot do a full bearer disable
here, since we cannot know when to enable it again unless
we have kept the bearer instance. Hopefully resolved the
atomicity problem (which I frankly don't see as a real
problem) as described in feedback from Ying.
Jon Maloy (4):
tipc: remove remnants of old broadcast code
tipc: eliminate buffer leak in bearer layer
tipc: stricter filtering of packets in bearer layer
tipc: reduce transmission rate of RESET messages when link is down
net/tipc/bearer.c | 88 +++++++++++++++++++++++++++++++++--------------------
net/tipc/bearer.h | 15 ---------
net/tipc/discover.c | 7 ++---
net/tipc/discover.h | 2 +-
net/tipc/link.c | 5 ++-
net/tipc/msg.h | 5 +++
6 files changed, 67 insertions(+), 55 deletions(-)
--
1.9.1
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140
_______________________________________________
tipc-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tipc-discussion