Re: Slow pthread_create() under high load

From: Alon Ziv (alonz@guidelet.com)
Date: Mon Mar 27 2000 - 13:29:40 EST


----- Original Message -----
From: Ulrich Drepper <drepper@redhat.com>
To: Khimenko Victor <khim@sch57.msk.ru>
Cc: <hb@sonique.com>; <rgooch@ras.ucalgary.ca>;
<linux-kernel@vger.rutgers.edu>
Sent: Monday, March 27, 2000 19:22
Subject: Re: Slow pthread_create() under high load

> "Khimenko Victor" <khim@sch57.msk.ru> writes:
>
> > AFAIK there are two issues: clone in 2.2 can not create sibling
> > (just child) and it'll lead to nasty problems since "parent" thread
> > can exit before "child" thread. In late 2.3.x it IS fixed.
>
> How do you think this should help? If you make all the threads
> siblings (of the initial thread), how should terminating one of them
> effect the others? If one threads dies of a SEGFAULT all the others
> must, too. Being siblings, they just continue to run. In the case of
> a normal multi-threaded application the parent will be the shell (or
> whatever program started the MT program). This program does not go on
> a reap the children.
>

This is solvable by simply making sure that all threads are children of the
manager thread, and having the manager take care of the reaping stuff. I
already had a patch that did this (from the early 2.3 days, when Tim Wragg
and I experimented with CLONE_PPID / CLONE_PPIDOK and ilk).

> --
> ---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
> Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> Red Hat `--' drepper at redhat.com `------------------------
>
> -
> 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/
>



-
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:20 EST