| Age | Commit message (Collapse) | Author |
|---|
|
is aligned just fine and in case we allocate the last piece of the
address space we don't want wrap-around to cause us to fail.
pointed out by and ok miod@
|
|
miod@ ok
|
|
(I'm reading code, that's where this comes from).
|
|
only binary change is the line numbers to asserts.
|
|
md5@ ok.
|
|
uvm_km_kmemalloc.
"should probbaly go in" millert@, "I think it should too" deraadt@
|
|
From mickey. art@ ok
|
|
i386 will use them soon and miod wants to work on other pmaps in
parallell.
miod@ ok
|
|
miod@ ok
|
|
miod@ ok
|
|
miod@ ok
|
|
|
|
ok beck miod pedro thib
|
|
- ansi-fy
- use struct vm_map * and struct vm_map_entry * instead of _t types
- fix some indentation problems.
miod@ ok
|
|
to separate locking, on most modern machines this is not enough
since operations on short types touch other short types that share the
same word in memory.
Merge pg_flags and pqflags again and now use atomic operations to change
the flags. Also bump wire_count to an int and pg_version might go
int as well, just for alignment.
tested by many, many. ok miod@
|
|
and make sure that nothing can ever be mapped at theses addresses.
Only i386 overrides the default for now.
From mickey@, ok art@ miod@
|
|
from mickey
|
|
in 15 years, make it a void function.
ok art@
|
|
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
|
|
Use a simple "rw_exit_read(); rw_enter_write();" for lock upgrade, since
that's what lockmgr did anyway.
deraadt@ ok
|
|
to "pg_flags" and "pg_version", so that they are a bit easier to work with.
Whoever uses generic names like this for a popular struct obviously doesn't
read much code.
Most architectures compile and there are no functionality changes.
deraadt@ ok ("if something fails to compile, we fix that by hand")
|
|
is proper errnos.
millert@ ok and some help
|
|
ok otto@
|
|
|
|
Cleanup the code accordingly.
ok pedro@, art@
|
|
eyeballed by miod@ and pedro@
|
|
by factoring most of the checks into a macro. OK otto@
|
|
ok kettenis@ cloder@ tom@ henning@
|
|
ok dim@
|
|
most agp_generic_bind_memory failures when memory is limited and very
fragmented.
In effect, this should fix a lot of X startup crashes after
activities that exercise memory a lot (e.g. make builds, building big
ports, etc).
ok mickey, miod
|
|
|
|
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@)
|
|
|
|
for cpu_swapin() on hppa* which is kept).
|
|
should never be referenced outside the context of the process to which
this stack belongs unless we do the PHOLD/PRELE dance. Loads of code
doesn't follow the rules here. Instead of trying to track down all
offenders and fix this hairy situation, it makes much more sense
to not swap kernel stacks.
From art@, tested by many some time ago.
|
|
pass zero; this will be used shortly. From art@
|
|
Okay weingart@, "I'm game with putting my name on it" dlg@
|
|
no change for normal code
|
|
miod@ ok
|
|
us did not see it or get a chance to test it before it was commited. It
broke cvs, in the ami driver, making it not succeed at seeing it's devices.
|
|
proper; found by krause and mmap_fixed
|
|
this results in lesse kva waste due to static preallocation of those
for every phys page and also every swap page.
tested by beck krw miod
|
|
|
|
|
|
will prevent panics in, e.g., bus_dmamem_alloc().
ok jason@ art@
|
|
defined; from NetBSD. Currently only used on xscale arm to use the mini data
cache for u area mappings instead of the main data cache.
|
|
|
|
1. drain hooks and lists of allocators make the code complicated
2. the only hooks in the system are the mbuf reclaim routines
3. if reclaim is actually able to put a meaningful amount of memory back
in the system, i think something else is dicked up. ie, if reclaiming
your ip fragment buffers makes the difference thrashing swap and not,
your system is in a load of trouble.
4. it's a scary amount of code running with very weird spl requirements
and i'd say it's pretty much totally untested. raise your hand if your
router is running at the edge of swap.
5. the reclaim stuff goes back to when mbufs lived in a tiny vm_map and
you could run out of va. that's very unlikely (like impossible) now.
ok/tested pedro krw sturm
|
|
as paddr_t could be a long long (soon) always cast and print as llx.
|
|
as freepages being vconverted back to byte address make sure to
perform calculations in (upcoming) larger paddr_t to avoid losing
higher bits in calculation.
|
