Whamcloud - gitweb
b=21574 PING_INTERVAL_SHORT should not postpone the next ping
authorJohann Lombardi <johann@sun.com>
Sat, 16 Jan 2010 14:27:17 +0000 (15:27 +0100)
committerJohann Lombardi <johann@sun.com>
Sat, 16 Jan 2010 14:27:17 +0000 (15:27 +0100)
commitff9e05ee9f36b50f0415adfbacbe54fb7eaa4639
treec34b0df83e5fc20ba4df5bf021dbcf3e59a90814
parent6f271946afa104952f56be86a9494eb8e1ec245e
b=21574 PING_INTERVAL_SHORT should not postpone the next ping

i=oleg
i=andrew

Most our tests run with obd_timeout=20s, so PING_INTERVAL=5s, while
PING_INTERVAL_SHORT=7s. ptlrpc_pinger_commit_expected() was actually
not intended to delay pings.
Although we would prefer to schedule the next ping after a
bit more than 5s (jbd commit time), using 5s instead of 7s
is not a big deal since we will have to only wait for 5
additional seconds in the worst case.
lustre/include/obd_support.h