From: "J . A . Magallon" <jamagallon@able.es>
To: Dave McCracken <dmccr@us.ibm.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Separate CLONE_PARENT and CLONE_THREAD behavior
Date: Thu, 25 Oct 2001 02:10:21 +0200 [thread overview]
Message-ID: <20011025021021.A2928@werewolf.able.es> (raw)
In-Reply-To: <117830000.1003951015@baldur>
In-Reply-To: <117830000.1003951015@baldur>; from dmccr@us.ibm.com on Wed, Oct 24, 2001 at 21:16:55 +0200
On 20011024 Dave McCracken wrote:
>
>Several versions back you added code that forces CLONE_PARENT behavior
>whenever CLONE_THREAD is specified. This unnecesarily forces a particular
>multi-threading model at the application level, and in fact breaks some
>ways of doing multi-threading.
>
>In particular, it requires that at least one task in an application *not*
>be part of the thread group, and that the pid returned by the original
>fork() can not be the thread group id itself.
>
>It would still be entirely possible to code an application or threading
>library in the way you envision by specifying CLONE_PARENT and CLONE_THREAD
>together. However, there's no good reason for forcing this model.
>
>A patch to remove that restriction is below.
>
Will this break current pthreads in glibc 2.2.4 ???
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.13-beo #2 SMP Thu Oct 25 00:59:08 CEST 2001 i686
next prev parent reply other threads:[~2001-10-25 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 19:16 [PATCH] Separate CLONE_PARENT and CLONE_THREAD behavior Dave McCracken
2001-10-25 0:10 ` J . A . Magallon [this message]
2001-10-25 13:24 ` Dave McCracken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011025021021.A2928@werewolf.able.es \
--to=jamagallon@able.es \
--cc=dmccr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox