In commit 10724cc7bb78 ("tipc: redesign connection-level flow control")
we replaced the previous message based flow control with one based on
1k blocks. In order to ensure backwards compatibility the mechanism
falls back to using message as base unit when it senses that the peer
doesn't support the
Hi Partha,
I rebuilt afresh and retried the test with the same lockup kernel dumps.
Yes I have multiple tipc clients subscribed to the topology server, at
least 10 clients.
They all use a subscription timeout of TIPC_WAIT_FOREVER
I will try the kernel command line parameter next week.
JT
On Fri
> -Original Message-
> From: Holger Brunck [mailto:holger.bru...@keymile.com]
> Sent: Thursday, 24 November, 2016 09:48
> To: tipc-discussion@lists.sourceforge.net
> Subject: [tipc-discussion] TIPC link statistic
>
> Hi all,
> I got a basic question to the link statistic printed out from T
Hi all,
I got a basic question to the link statistic printed out from TIPC when I use
"tipc-config -ls" or "tipc link stat show".
I got a link between a PPC board running kernel 4.4 and my local x86 PC via
ethernet bearers. I have a simple server running on my PPC board listening on a
TIPC socket
Hi John,
Do you have several tipc clients subscribed to topology server?
What subscription timeout do they use?
Please enable kernel command line parameter:
softlockup_all_cpu_backtrace=1
/Partha
On 11/23/2016 11:04 PM, John Thompson wrote:
> Hi Partha,
>
> I tested overnight with the 2 patches
