Ok and I am sorry btw !
--
Jog
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Is my question clear, or would you like me to give further info (and which) ?
Thanks
--
Jog
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...
Hello,
I am learning the freebsd way to keep the time up to date.
We avoid to call hardware hardclock() every time we need a timestamp by
applying some math. I get the idea.
But, how do we know how far we are from the last hardclock()?
Are the updates to the "fake" timestamps occuring at a cons
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
OK.
I read the document and understood it I guess.
Very interesting, and well engineered.
On x86/i386/amd64, could not all this be replaced by a simple call to apic
timer ?
We would get the timestamp, we can even store it, make calculation on top of it.
My jugement may miss something important
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Hi,
Currently I read more about timers and clock.
I am struggling on one field of a struct :
http://fxr.watson.org/fxr/source/kern/kern_tc.c?v=FREEBSD10#L63
I would like to understand what th_generation means please.
Thanks a lot
--
Jog
___
freebsd