Still running good ol' 4.2a on an F230:
Sun Apr 18 21:00:00 EDT [statd]: 9:00pm up 497 days, 1:10 407777519 NFS ops, 0 CIFS ops, 0 HTTP ops Sun Apr 18 22:00:00 EDT [statd]: 10:00pm up 497 days, 2:10 408458997 NFS ops, 0 CIFS ops, 0 HTTP ops Sun Apr 18 23:00:00 EDT [statd]: 11:00pm up 42 mins, 409036765 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Apr 19 00:00:00 EDT [statd]: 12:00am up 1:42 409494263 NFS ops, 0 CIFS ops, 0 HTTP ops
This looks like 2^32 ticks elapsed (about 42949673 seconds)... is this one of the counters being increased to 64 bits?
Still running good ol' 4.2a on an F230:
Sun Apr 18 21:00:00 EDT [statd]: 9:00pm up 497 days, 1:10 407777519 NFS ops, 0 CIFS ops, 0 HTTP ops Sun Apr 18 22:00:00 EDT [statd]: 10:00pm up 497 days, 2:10 408458997 NFS ops, 0 CIFS ops, 0 HTTP ops Sun Apr 18 23:00:00 EDT [statd]: 11:00pm up 42 mins, 409036765 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Apr 19 00:00:00 EDT [statd]: 12:00am up 1:42 409494263 NFS ops, 0 CIFS ops, 0 HTTP ops
This looks like 2^32 ticks elapsed (about 42949673 seconds)...
Yes, the tick counter is 32 bits in 4.2a:
tooting$ egrep sk_tics ../sk/*.h ../sk/sk.h:extern VOLATILE int4 sk_tics; /* number of ticks since boot */
is this one of the counters being increased to 64 bits?
It's not been increased in size yet; I don't know if it's one of the ones we plan to boost in size.