| Age | Commit message (Collapse) | Author |
|---|
|
value (based on physmem) is below NKMEMPAGES_MIN, we are on a low memory
machine and can not afford more anyway.
ok deraadt@ tedu@
|
|
changes the pressure on the uvm system, uncovering several bugs. Some
of those bugs result in provable deadlocks. We'll have to reconsider
integrating this diff again after fixing those bugs.
ok art@
|
|
instead of M_NOWAIT. Checking for M_NOWAIT made many malloc calls that used
that flag actually wait. This probably explains many if the strange hangs
people have seen recently.
ok miod@
|
|
|
|
This will allow us to escape the limitations of kmem_map.
At this moment, the per-type limits are still enforced for all sizes,
but we might loosen that limit in the future after some thinking.
Original diff from Mickey in kernel/5761 , I massaged it a little to
obey the per-type limits.
miod@ ok
|
|
From NetBSD, kindly pointed out by YAMAMOTO Takashi.
ok miod@
|
|
help and ok miod@ thib@
|
|
But the reason for this isn't some kind of "we can make it use the
pre-zeroed pages and zero the freelist in the idle loop and OMG I can
has optimisatiuns" which would require tons of infrastructure and make
everything slower.
The reason is that it shrinks other code. And that's good.
dlg@ ok, henning@ ok (before he read the diff)
|
|
version for i386
more architectures and ctob() replacement is being worked on
prodded by and ok miod
|
|
Pick reasonble names for the locks involved..
ok tedu@, art@
|
|
and make sure that nothing can ever be mapped at theses addresses.
Only i386 overrides the default for now.
From mickey@, ok art@ miod@
|
|
kmem_object) just so that we can remove them, just use pmap_extract
to get the pages to free and simplify a lot of code to not deal with
the list of intrsafe maps, intrsafe objects, etc.
miod@ ok
|
|
|
|
In this commit:
- gdt lock on amd64
- sysctl lock
- malloc sysctl lock
- disk sysctl lock
- swap syscall lock
miod@, pedro@ ok (and "looks good" others@)
|
|
M_CANFAIL, idea from miod@, okay deraadt@
|
|
return NULL instead of panic()'ing.
ok pedro@, deraadt@
|
|
useful; miod@ ok
|
|
'go for it' deraadt@
|
|
of panics and bugfixes. Access curproc directly, do not expect a process
pointer as an argument. Should fix many "process context required" bugs.
Incentive and okay millert@, okay marc@. Various testing, thanks.
|
|
arches; except on sparc where the range is 4-8 for !sun4m and 4-64 for sun4m,
selected at runtime.
|
|
scenarios, instead generating an ENOMEM backfeed, ok tedu@, prodded by many
|
|
|
|
from form@pdp-11.org.ru via mpech. ok millert
|
|
less error prone (no wraparound). no real functional change though.
ok markus tdeval
|
|
takes a void *. convert uiomove to take a void * as well. ok deraadt@
|
|
|
|
rescinded 22 July 1999. Proofed by myself and Theo.
|
|
uses it as a hint for where to steal space from the parent map. We've been
passing random stack garbage as that hint for ages. It's a wonder it didn't
break things until we started working on Hammer.
noone objected for at least a week.
|
|
|
|
change intended.
|
|
|
|
|
|
okay art@
|
|
|
|
machines or some configurations or in some phase of the moon (we actually
don't know when or why) files disappeared. Since we've not been able to
track down the problem in two weeks intense debugging and we need -current
to be stable, back out everything to a state it had before UBC.
We apologise for the inconvenience.
|
|
the future that wants to allocate pv entries for every pmap_enter and wants
to allocate those pv entries from kmem_map, it might be a good idea to
init the kmem_map before initializing the kmemusage struct (because kmemusage
allocates memory).
|
|
date: 2000/02/11 19:22:52; author: thorpej;
Add some very simple code to auto-size the kmem_map. We take the
amount of physical memory, divide it by 4, and then allow machine
dependent code to place upper and lower bounds on the size. Export
the computed value to userspace via the new "vm.nkmempages" sysctl.
NKMEMCLUSTERS is now deprecated and will generate an error if you
attempt to use it. The new option, should you choose to use it,
is called NKMEMPAGES, and two new options NKMEMPAGES_MIN and
NKMEMPAGES_MAX allow the user to configure the bounds in the kernel
config file.
|
|
Contains also support for page coloring.
|
|
vm_map_t -> struct vm_map *
vm_map_entry_t -> struct vm_map_entry *
simple_lock_data_t -> struct simplelock
(uvm not done yet, coming in the next commit)
|
|
(Look ma, I might have broken the tree)
|
|
|
|
useful changes (and a lot of cleanup). Bring in them.
|
|
|
|
I know at least of two cases where people got confused by this and used
the wrong size to the malloc debugger.
|
|
|
|
|
|
|
|
|
|
hw.diskstats/hw.disknames.
|
|
|
