Re: Changing p_swtime and td_slptime to ticks

Jeff Roberson wrote:
On Mon, 17 Sep 2007, Julian Elischer wrote:

Jeff Roberson wrote:
Enclosed is a patch that fixes swapping with ULE. ULE has never properly set p_swtime and td_slptime which are used by the swapout/swapin code to select the appropriate thread to swap.

I have not looked at in the depth required, but 2 points that I was unable
to check to my satisfaction before I got called away for work....

1/ the source of the ticks is a monotonically increasing count that never
goes backwards or changes?

ticks is incremented each time hardclock() is called. That's it.


2/ nothing that used to be accounted in seconds becomes accounted for in ticks?

I scale back to seconds where it is required. Really I think ticks would be the better metric in vm_glue.c but didn't want to make any drastic changes.

ticks is 2^31 on x86 and at HZ=1000 is wraps within a reasonable
short uptime. You have to make sure that your code handles that
correctly or you run into lots of strange effects which are almost
impossible to reproduce. In TCP we've got bitten by that.

--
Andre
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Changing p_swtime and td_slptime to ticks
    ... set p_swtime and td_slptime which are used by the swapout/swapin code to select the appropriate thread to swap. ... 1/ the source of the ticks is a monotonically increasing count that never ... ULE does not have a once per-second loop iterating over all threads. ... This change does make it possible to use sub-second granular decisions in the swap code, however I'm not sure if that's really necessary. ...
    (freebsd-arch)
  • Re: Changing p_swtime and td_slptime to ticks
    ... properly set p_swtime and td_slptime which are used by the swapout/swapin code to select the appropriate thread to swap. ... 2/ nothing that used to be accounted in seconds becomes accounted for in ticks? ... ULE does not have a once per-second loop iterating over all threads. ... This change does make it possible to use sub-second granular decisions in the swap code, however I'm not sure if that's really necessary. ...
    (freebsd-arch)
  • Re: Changing p_swtime and td_slptime to ticks
    ... set p_swtime and td_slptime which are used by the swapout/swapin code to ... In 4BSD these two variables are increment once per-second as schedcpu ... legacy meaning by subtracting from ticks and dividing by hz. ... swap code, however I'm not sure if that's really necessary. ...
    (freebsd-arch)
  • 64bit ticks, was Re: Changing p_swtime and td_slptime to ticks
    ... properly set p_swtime and td_slptime which are used by the swapout/swapin code to select the appropriate thread to swap. ... 1/ the source of the ticks is a monotonically increasing count that never ... Really I think ticks would be the better metric in vm_glue.c but didn't want to make any drastic changes. ...
    (freebsd-arch)
  • Re: Changing p_swtime and td_slptime to ticks
    ... set p_swtime and td_slptime which are used by the swapout/swapin code to select the appropriate thread to swap. ... 1/ the source of the ticks is a monotonically increasing count that never ... Really I think ticks would be the better metric in vm_glue.c but didn't want to make any drastic changes. ...
    (freebsd-arch)