DragonFly kernel List (threaded) for 2003-12
Re: libcaps thread testing code committed
Just got back from yet another business trip so I am behind on my
On Dec 6, 2003, at 10:49 PM, Matthew Dillon wrote:
Thread testing code has been committed for libcaps. Note that the
regs are not saved and restored yet (though there is assembly to
present). I did some preliminary switch overhead tests with fp
restore and without. 2 million lwkt_swich() calls execute in 0.15
second while the same test which also saves and restore FP regs ran
in 0.45 seconds. So it's the difference between
and 225ns/context-switch (on an AMD-64).
Awesome :). I guess I can get started with some examples soon then.
is I've been handed a flurry of work to complete in the next two weeks
Christmas vacation begins and I won't have a dragonfly PC around to
[unless it works on PowerPC :)].
System call messaging (Galen is working on this)
Might have to wait for this anyway...
Libcr sync from libc, and libcr tie-ins for mp_lock
(e.g. using get_mplock() and rel_mplock())
Haven't had coffee yet so this looks like Sanskrit... moving on.
Other lock or mutex functionality to support the new libcr.
Kernel asynchronous syscall messaging support.
So its all synchronous at the moment? Does this mean there are no
queues or that, as in cooking, all the prep is done and we just need the
proper recipe to combine the ingredients to bake up some asynchronous
This commit 'proves out' the upcall API fairly well. I was able to
implement all the infrastructure necessary to support user
including IPI's between virtual cpus (rfork'd processes), without
having to drop into the kernel to performing a thread switch.