on 06/12/2010 21:01 Jung-uk Kim said the following: > :-) Don't get me wrong, I generally agree with you *iff* it does not > hurt too much. Anyway, this issue should be resolved from the root, > i.e., kern_resouce.c, if possible.
But what to resolve there? I just want to always have a stable source "cpu ticks", and then everything else should just work? BTW, if someone comes up with a patch for more or less correct accounting when "cpu ticks" frequency is allowed to change, then I am all for it. But, IMO, it's just easier to use stable "cpu ticks". -- Andriy Gapon _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
