Age | Commit message (Collapse) | Author |
|
UBC, but prerequsites for it.
- Create a daemon that processes async I/O (swap and paging in the future)
requests that need processing in process context and that were processed
in the pagedaemon before.
- Convert some ugly ifdef DIAGNOSTIC code to less intrusive KASSERTs.
- misc other cleanups.
|
|
for the virtual address.
|
|
(Look ma, I might have broken the tree)
|
|
instead of doing fork1, cpu_set_kpc. This lets us retire cpu_set_kpc and
avoid a multiprocessor race.
This commit breaks vax because it doesn't look like any other arch, someone
working on vax might want to look at this and try to adapt the code to be
more like the rest of the world.
Idea and uvm parts from NetBSD.
|
|
- Use malloc/free instead of MALLOC/FREE for variable sized allocations.
- Move the memory inheritance code to sys/mman.h and rename from VM_* to MAP_*
- various cleanups and simplifications.
|
|
occurs on the fs with large block size. We can have situation where
numcleanbufs < locleanbufs and numdirtybufs < hidirtybufs. So, buffer
flushing daemon never wakeups and other processes asleep forever waiting
for a clean buffers. We count pages only for the dirty buffers which are
on freelist(BQ_DIRTY).
niklas@ found this.
Rename flasher to cleaner. Suggested by costa@.
Discussed with niklas@, costa@, millert@, art@.
Ok deraadt@.
|
|
start of raid autoconfiguration thread. Required for upcoming RAIDFrame
code update.
From Thierry Deval <TDeval@PrimeOBJ.COM>
|
|
problem when syncer can't do its work because of vnode locks (PR1983).
This also solves our problem where bigger number of buffers results in a
much worse perfomance. In my configuration (i386, 128mb, BUFCACHEPERCENT=35)
this speedup tar -xzf ports.tar.gz in 2-4 times. In configuration with
low number of buffers and softupdates this may slowdown some operations
up to 15%.
The major difference with current buffer cache is that new implementation
uses separate queues for dirty and clean buffers. I.e. BQ_LRU and BQ_AGE
replaced by BQ_CLEAN and BQ_DIRTY. This simplifies things a lot and
doesn't affect perfomance in a bad manner.
Thanks to art and costa for pointing on errors.
Tested by brad, millert, naddy, art, jj, camield
art, millert ok.
|
|
|
|
|
|
|
|
systems which want configuration to finish late, like I2O. Implemented via
a general hooks mechanism which the shutdown hooks have been converted to
use as well. It even has manpages!
|
|
everywhhere.
|
|
|
|
|
|
|
|
inside OpenSSL codebase
|
|
|
|
|
|
okay art@ miod@
|
|
|
|
Move it from cpu_startup() to main().
|
|
|
|
on NetBSD's code, as well as some faked Posix RT extensions by me. This makes
at least simple linuxthreads tests work.
|
|
|
|
instead of a home-brew equivalent.
|
|
|
|
|
|
This is not a perfect solution.
|
|
|
|
|
|
cpu_exit no longer frees the vmspace and u-area. This is now handled by a
separate kernel thread "reaper". This is to avoid sleeping locks in the
critical path of cpu_exit where we're not allowed to sleep.
From NetBSD
|
|
The function and the argument never change.
|
|
|
|
|
|
|
|
idea is to support various cryptographic hardware accelerators (which
may be (detachable) cards, secondary/tertiary/etc processors,
software crypto, etc). Supports session migration between crypto
devices. What it doesn't (yet) support:
- multiple instances of the same algorithm used in the same session
- use of multiple crypto drivers in the same session
- asymmetric crypto
No support for a userland device yet.
IPsec code path modified to allow for asynchronous cryptography
(callbacks used in both input and output processing). Some unrelated
code simplification done in the process (especially for AH).
Development of this code kindly supported by Network Security
Technologies (NSTI). The code was writen mostly in Greece, and is
being committed from Montreal.
|
|
http://www.usenix.org/publications/library/proceedings/usenix98/banga.html
|
|
|
|
|
|
argument. Let sys_rfork build the arguments to fork1() and do the
sanity checks itself.
|
|
|
|
|
|
from. Hopefully this will fix all the hangs/panics where the root device
was not found.
|
|
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.
|
|
|
|
|
|
|
|
|
|
|