Hi,
On Sun, Mar 26, 2000 at 01:33:43PM +0300, sinisa@mysql.com wrote:
>
> I understood (or misunderstood) Mr. Cox notes that when a new thread
> is created, scheduler goes through all existing threads and changes
> their time slice / priority , in order to accomodate a new thread in a
> fair manner.
No, not at all. Only the parent and child are involved in the fork
itself, although we may have to consider the priority of other runnable
tasks when we first come to scheduled the child.
> Regarding POSIX threads being "braindamaged pile of crap", it is
> unfortunately the only available standard for writing relatively
> platform - independent multithreaded servers.
Maybe, but although a lot of the POSIX threads are reasonable, things
like requiring uid/gid updates to be instantly effective across all
threads in the process are just insane. There ain't no way that's
going into the kernel any time soon: it would require adding semaphore
locking to all of the credential information that is currently task-
local.
--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Mar 31 2000 - 21:00:19 EST