Branch: refs/heads/stable1-proposed
Home:
https://github.com/kronosnet/kronosnet
Commit: fa63b127bac3c6169407dd0d4d15ba2f0d503ba5
https://github.com/kronosnet/kronosnet/commit/fa63b127bac3c6169407dd0d4d15b…
Author: Fabio M. Di Nitto <fdinitto(a)redhat.com>
Date: 2023-09-25 (Mon, 25 Sep 2023)
Changed paths:
M libknet/links.c
M libknet/tests/api_knet_link_set_ping_timers.c
Log Message:
-----------
links: fix ping interval and pong timeout value checking
warn if ping interval is lower than thread timer resolution as
it has no effects
error if ping timeout is lower than thread timer resolution as
it causes links to be highly unstable
Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com>
Commit: cb96e3aa85799b6b2c74a645af6cc7e494f7f811
https://github.com/kronosnet/kronosnet/commit/cb96e3aa85799b6b2c74a645af6cc…
Author: Fabio M. Di Nitto <fdinitto(a)redhat.com>
Date: 2023-09-25 (Mon, 25 Sep 2023)
Changed paths:
M libknet/threads_rx.c
Log Message:
-----------
rx: allow links to be active faster
scenario: node A and node B
node A completes ping/pong link up process faster than B
node A starts to send data to node B
old behavior: node B would unconditionally discard data packets
new behavior:
node B will check internal link status to see if ping/pong link up
process is in progress.
if the link is sending pings and receiving pongs, it´s safe to assume
that the link will go up (since we are also receiving data from the
node A). node B will speed up link up and accept data immediately.
This should address a overall init race condition when nodes startup
are slighly off by enough milliseconds to cause 2 memeberships to form
and see fencing fireworks.
Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com>
Compare:
https://github.com/kronosnet/kronosnet/compare/cae7cafa5f03...cb96e3aa8579