diff options
author | Artur Grabowski <art@cvs.openbsd.org> | 2008-07-02 15:21:34 +0000 |
---|---|---|
committer | Artur Grabowski <art@cvs.openbsd.org> | 2008-07-02 15:21:34 +0000 |
commit | d034dde8db4cec62e959d1b5800dbf696d646924 (patch) | |
tree | 78d1c7c906ee567135863b97a0e079718240d96b /usr.sbin/acpidump | |
parent | 3c56feb2b4ddf8f30afb1bbd4050a0cf5dde192e (diff) |
Make the pagedaemon a bit happier.
1. When checking if the pagedaemon should be awakened and to see how
much work it should do, consider the buffer cache deficit
(how much pages the buffer cache can eat max vs. how much it has
now) as pages that are not free. They are actually still usable by
the allocator, but the presure on the pagedaemon is increased when
we starting to chew into the memory that the buffer cache wants to
use.
2. Remove the stupid 512kB limit of how much memory should be our
free target. That maybe made sense on 68k, but on modern systems
512k is just a joke. Keep it at 3% of physical memory just like
it was meant to be.
3. When doing allocations for the pagedaemon, always let it use the
reserve. the whole UVM_OBJ_IS_KERN_OBJECT is silly and doesn't
work in most cases anyway. We still don't have a reserve for
the pagedaemon in the km_page allocator, but this seems to help
enough. (yes, there are still bad cases in that code and the comment
is only half-true, the whole section needs a massage, but that will
happen later, this diff only touches pagedaemon parts)
Testing by many, prodded by theo.
Diffstat (limited to 'usr.sbin/acpidump')
0 files changed, 0 insertions, 0 deletions