On Sun, Jan 21, 2018 at 9:22 PM, Ian Lepore <i...@freebsd.org> wrote:

> On Sun, 2018-01-21 at 22:07 +0100, Hans Petter Selasky wrote:
> > On 01/21/18 21:45, Johannes Lundberg wrote:
> > >
> > > What does kern.eventtimer.periodic do?  The sysctl description
> > > wasn't
> > > that elaborate...
> > It turns off re-programming the timer every time there is a new
> > callout
> > with earlier completion time.
> >
> > --HPS
>
> Well, it does more than that.  It makes the system run "the old way"
> where there are periodic timer interrupts that happen whether they need
> to or not (bad for power saving), and there's no way to schedule
> anything to happen on intervals other than when the periodic ticks
> occur (so if kern.hz = 1000 and you ask to sleep for a microsecond you
> may actually sleep up to a millisecond).
>
>
Thanks for the further explanation.
I curious as to where the problem might be though.. It is the game's
binary-only Linux executable (Unreal Engine 2.5), Linux SDL 1.2, or on the
FreeBSD side? Haven't experienced anything similar with Quake3...
Switching to periodic timer feels like overkill but it does the job as a
work around.



> -- Ian
>
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to