Commits September 2023

Branch: refs/heads/fast-link-up-stable1-proposed Home: https://github.com/kronosnet/kronosnet Commit: cbab84f47095ca51391157d36859f0548889fefd https://github.com/kronosnet/kronosnet/commit/cbab84f47095ca51391157d36859f… Author: Fabio M. Di Nitto <fdinitto(a)redhat.com> Date: 2023-09-19 (Tue, 19 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 internval is lower than thread time resolution as it has no effects error if point timeout is lower than thread time resoltuion as it causes links to be highly unstable Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com> Commit: f0843b5a4f81e5637a2e7ef4c5b3b6222ada6bcf https://github.com/kronosnet/kronosnet/commit/f0843b5a4f81e5637a2e7ef4c5b3b… Author: Fabio M. Di Nitto <fdinitto(a)redhat.com> Date: 2023-09-19 (Tue, 19 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/cbab84f47095%5E...f0843b5a4f…

1 year, 3 months

[jenkins] kronosnet PR-416 (build 2) success

by jenkins＠kronosnet.org

total runtime: 38 min Coverity results: http://ci.kronosnet.org/coverity/kronosnet/rhel9-coverity-x86-64/pr416/2/ Split logs: https://ci.kronosnet.org/job/kronosnet/job/kronosnet-pipeline/job/PR-416/2/… Full log: https://ci.kronosnet.org/job/kronosnet/job/kronosnet-pipeline/job/PR-416/2/…

1 year, 3 months

[kronosnet/kronosnet] 03e36e: threads: add config check to match min value with ...

by Fabio M. Di Nitto

Branch: refs/heads/fast-link-up Home: https://github.com/kronosnet/kronosnet Commit: 03e36e80b2a3ed269d89354c93761c989dc3d3eb https://github.com/kronosnet/kronosnet/commit/03e36e80b2a3ed269d89354c93761… Author: Fabio M. Di Nitto <fdinitto(a)redhat.com> Date: 2023-09-19 (Tue, 19 Sep 2023) Changed paths: M libknet/tests/api_knet_handle_set_threads_timer_res.c M libknet/threads_common.c Log Message: ----------- threads: add config check to match min value with pong timeouts avoids network instability and dump full report of nodes/links that would have caused problems Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com>

1 year, 3 months

[jenkins] kronosnet PR-416 (build 1) success

by jenkins＠kronosnet.org

total runtime: 38 min Coverity results: http://ci.kronosnet.org/coverity/kronosnet/rhel9-coverity-x86-64/pr416/1/ Split logs: https://ci.kronosnet.org/job/kronosnet/job/kronosnet-pipeline/job/PR-416/1/… Full log: https://ci.kronosnet.org/job/kronosnet/job/kronosnet-pipeline/job/PR-416/1/…

1 year, 3 months

[kronosnet/kronosnet] 8af217: links: fix ping interval and pong timeout value ch...

by Fabio M. Di Nitto

Branch: refs/heads/fast-link-up Home: https://github.com/kronosnet/kronosnet Commit: 8af21789096e4ee298ab5d69a066d913a06663d7 https://github.com/kronosnet/kronosnet/commit/8af21789096e4ee298ab5d69a066d… Author: Fabio M. Di Nitto <fdinitto(a)redhat.com> Date: 2023-09-19 (Tue, 19 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 internval is lower than thread time resolution as it has no effects error if point timeout is lower than thread time resoltuion as it causes links to be highly unstable Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com> Commit: 40834983d8ffef779061b314ba79352b36a19928 https://github.com/kronosnet/kronosnet/commit/40834983d8ffef779061b314ba793… Author: Fabio M. Di Nitto <fdinitto(a)redhat.com> Date: 2023-09-19 (Tue, 19 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/e10adcfec424...40834983d8ff

1 year, 3 months

[kronosnet/kronosnet] e10adc: rx: allow links to be active faster

by Fabio M. Di Nitto

Branch: refs/heads/fast-link-up Home: https://github.com/kronosnet/kronosnet Commit: e10adcfec424f04823ac252bb710c0d390acef63 https://github.com/kronosnet/kronosnet/commit/e10adcfec424f04823ac252bb710c… Author: Fabio M. Di Nitto <fdinitto(a)redhat.com> Date: 2023-09-19 (Tue, 19 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>

1 year, 3 months

← Newer
1
...
22
23
24
25
26
27
28
...
94
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Commits September 2023