Page MenuHomeFreeBSD

hardclock.9: Refine some details
ClosedPublic

Authored by imp on Jul 1 2021, 3:56 PM.

Details

Summary

Refine mistakes from adaptaton of NetBSD's hardclock man page to
FreeBSD:
o clarify what usermode means
o clarify how often hardclock is called
o remove Xr callout(9) since that's done elsewhere

Sponsored by: Netflix

Diff Detail

Repository
rG FreeBSD src repository
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

imp requested review of this revision.Jul 1 2021, 3:56 PM
share/man/man9/hardclock.9
41–42

This is too vague as for me. We could specify that it is called hz times per second when system is busy, but at least twice per second when idle.

mav: how does my suggestion sound?

share/man/man9/hardclock.9
41–42

hardclock is called adaptively based on pending work. The rate ranges from hz times a second for a very busy system, to as few as twice a second for an idle system. When calls at tick boundaries are omitted, cnt reflects an estimate of the number of elapsed ticks since the last call. Over the long haul, the sum of the cnt argument to this function over a second averages hz, however hz(9) has details important for short time scales.

To replace everything in this section down to the usermode argument.

update to a variation of what I suggested...

This revision is now accepted and ready to land.Jul 1 2021, 7:16 PM
share/man/man9/hardclock.9
42

"rate"?

imp marked 2 inline comments as done.Jul 1 2021, 7:20 PM
imp added inline comments.
share/man/man9/hardclock.9
42

yes. Unless there's other changes, though, I'll not push an update to fix it (I've fixed it locally)

This revision was automatically updated to reflect the committed changes.
imp marked an inline comment as done.