Age | Commit message (Collapse) | Author |
|
|
|
add more support for external managers
|
|
|
|
|
|
|
|
|
|
|
|
from. Hopefully this will fix all the hangs/panics where the root device
was not found.
|
|
|
|
|
|
|
|
They do the same thing, but the former is noticeably faster on sparc
|
|
|
|
|
|
problems when stathz runs at different speed than hz/profhz.
|
|
|
|
|
|
an uninitialized variable; art@stacken.kth.se
|
|
|
|
to, at the bottom or the top, depending on your architecture's stack growth
direction. This is in preparation for Linux' clone(2) emulation.
port maintainers, please check that I did the work right.
|
|
commit messages:
Scheduler bug fixes and reorganization
* fix the ancient nice(1) bug, where nice +20 processes incorrectly
steal 10 - 20% of the CPU, (or even more depending on load average)
* provide a new schedclock() mechanism at a new clock at schedhz, so high
platform hz values don't cause nice +0 processes to look like they are
niced
* change the algorithm slightly, and reorganize the code a lot
* fix percent-CPU calculation bugs, and eliminate some no-op code
=== nice bug === Correctly divide the scheduler queues between niced and
compute-bound processes. The current nice weight of two (sort of, see
`algorithm change' below) neatly divides the USRPRI queues in half; this
should have been used to clip p_estcpu, instead of UCHAR_MAX. Besides
being the wrong amount, clipping an unsigned char to UCHAR_MAX is a no-op,
and it was done after decay_cpu() which can only _reduce_ the value. It
has to be kept <= NICE_WEIGHT * PRIO_MAX - PPQ or processes can
scheduler-penalize themselves onto the same queue as nice +20 processes.
(Or even a higher one.)
=== New schedclock() mechanism === Some platforms should be cutting down
stathz before hitting the scheduler, since the scheduler algorithm only
works right in the vicinity of 64 Hz. Rather than prescale hz, then scale
back and forth by 4 every time p_estcpu is touched (each occurance an
abstraction violation), use p_estcpu without scaling and require schedhz
to be generated directly at the right frequency. Use a default stathz (well,
actually, profhz) / 4, so nothing changes unless a platform defines schedhz
and a new clock.
[ To do: Define these for alpha, where hz==1024, and nice was totally broke.]
=== Algorithm change === The nice value used to be added to the
exponentially-decayed scheduler history value p_estcpu, in _addition_ to
be incorporated directly (with greater weight) into the priority calculation.
At first glance, it appears to be a pointless increase of 1/8 the nice
effect (pri = p_estcpu/4 + nice*2), but it's actually at least 3x that
because it will ramp up linearly but be decayed only exponentially, thus
converging to an additional .75 nice for a loadaverage of one. I killed
this: it makes the behavior hard to control, almost impossible to analyze,
and the effect (~~nothing at for the first second, then somewhat increased
niceness after three seconds or more, depending on load average) pointless.
=== Other bugs === hz -> profhz in the p_pctcpu = f(p_cpticks) calcuation.
Collect scheduler functionality. Try to put each abstraction in just one
place.
|
|
|
|
|
|
|
|
|
|
|
|
disappear (detach is coming).
|
|
|
|
|
|
other siblings.
|
|
|
|
even if they happen to own them at the moment.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
sure that the fd_freefile hints stay in sync, otherwise free file
descriptors might not be overlooked by fdalloc(); ok millert@
|
|
clean up the debug functions
add simple_lock_assert
|
|
|
|
It applies the supplied function f(state, p, len) to every contiguous region
in a mbuf, thus mostly handling all the mbuf-isms for you.
It's used by my TCP MD5 signature implementation to run MD5 over the TCP
payload data in a mbuf so that I don't have to spread mbufism-loops all over.
It might also be useful for IPsec.
|
|
no /dev/arandom.
|
|
Original work done in FreeBSD, but this code was ported from NetBSD by
Chuck Cranor.
|
|
vmstat will fail if we don't have symbol even when it doesn't need it. XXX
|
|
|
|
|
|
|
|
|