How about the abilty for multiple threads to execute at the same time? :)

The double negative implies that we would not add functionality that might be desired.

The resources are *all* shared (not just file resources), but each thread has it's own thread-specific stack.

Who's we white-man? (That's a very American joke for our international readers). I'd like to here from the 'kernel architects', who have been completely silent on the topic of kernel threads up til this point. (And not just in the context of this discussion, they've been mostly silent for months, if not years on this topic, except to say that they don't like Richard's solution..)

Another thing I'd like to add to the requirements list is that the threads use 'standard' threading mechanisms for safety, such as mutex/semaphore, etc.., which should exist in the kernel as well.

This is inline with the Posix stuff, and rather than invent our 'own' new kind of data structure, I'd like to stick with known solutions that work and everyone for the most part understands.

Howeer, that requirement may be more detailed oriented than what you are looking for now.

Nate

To Unsubscribe: send mail to majo...@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message