Junliang,
Hi all, From this mail list , I found some guys had done many latency tests with totem protocol. And in corosync configuration file , all parameters are set in millisecond's(ms) level. I just wonder if it could be
It's impossible directly from configuration file. And in a code such change would be quite difficult. If you want to try, take a look to qb_loop_timer_add calls (and specially QB_TIME_NS_IN_MSEC constant).
possible for us to tune corosync in microsecond's(1/1000 ms) level, of course, only for two nodes' case(connect two nodes directly without switches or routers). Maybe it doesn't make sense to use corosync in such "real time" case.
Honestly, I don't think corosync will work with such a small timeouts. From time to time it's even problematic to create membership with default 1sec timeout. Also Linux is not very real time, and (for example) IO can kill "realtime" behavior.
Just for curiosity, what are you trying to achieve? Having shorter then minimal 30 ms for failure detection or something else?
Regards, Honza
Thanks, Junliang Li _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
