[tipc-discussion] [PATCH net-next v3 1/4] tipc: remove remnants of old broadcast code

We remove a couple of leftover fields in struct tipc_bearer. Those were used by the old broadcast implementation, and are not needed any longer. There are no functional changes in this commit. Signed-off-by: Jon Maloy --- net/tipc/bearer.h | 15 --- 1 file changed, 15 deletions(-) d

[tipc-discussion] [PATCH net-next v3 4/4] tipc: reduce transmission rate of RESET messages when link is down

When a link is down, it will continuously try to re-establish contact with the peer by sending out a RESET message at each timeout interval. The default value for this interval is currently 375 ms. This is wasteful, and may become a problem in very large clusters with dozens or hundereds of nodes b

[tipc-discussion] [PATCH net-next v3 3/4] tipc: stricter filtering of packets in bearer layer

Resetting a bearer/interface, with the consequence of resetting all its pertaining links, is not an atomic action. This becomes particularly evident in very large clusters, where a lot of traffic may happen on the remaining links while we are busy shutting them down. In extreme cases, we may even s

[tipc-discussion] [PATCH net-next v3 2/4] tipc: eliminate buffer leak in bearer layer

When enabling a bearer we create a 'neigbor discoverer' instance by calling the function tipc_disc_create() before the bearer is actually registered in the list of enabled bearers. Because of this, the very first discovery broadcast message, created by the mentioned function, is lost, since it cann

[tipc-discussion] [PATCH net-next v3 0/4] some small fixes

When running TIPC in large clusters we experience behavior that may potentially 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 descriptio

Re: [tipc-discussion] subscr.c: Added new function is removed on latest: why

This was corrected the next day in: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/net/tipc/subscr.c?id=810813c47a564416f6306ae214e2661366c987a7 The topology server patch series were ready ar

Re: [tipc-discussion] kernel page allocation problem

On Wednesday 30 March 2016 14:40:58 Jon Maloy wrote: > Hi Leon, > I took a quick look at your dump, and to me it looks like you have simply run out of memory. I think that is the first thing you should look at. > As for the most recent code version to use, I cannot give you aby definite answer, s

Re: [tipc-discussion] kernel page allocation problem

Hi Leon, I took a quick look at your dump, and to me it looks like you have simply run out of memory. I think that is the first thing you should look at. As for the most recent code version to use, I cannot give you aby definite answer, since the kernel API and environment keeps changing continuo

Re: [tipc-discussion] subscr.c: Added new function is removed on latest: why

Guna, Thanks for pointing this out. This is a merge error from net to net-next, which has reverted the topology server patch series. The net updates were applied instead of net-next. I will inform netdev about this. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/net/tipc/s

Re: [tipc-discussion] kernel page allocation problem

Hi, Jon. Thank you for the reply. I can't upgrade the kernel to any other version, because it is an embedded system based on TI DM8148 processor and there are a lot of drivers and firmware working with it. As far as I understand, I can change/upgrade the TIPC files only. But I wasn't able to fi