From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: [patch] clone_startup(), 2.5.31-A0
Date: Tue, 13 Aug 2002 17:05:22 +0100 [thread overview]
Message-ID: <20020813170522.A12224@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0208130852450.7291-100000@home.transmeta.com>; from torvalds@transmeta.com on Tue, Aug 13, 2002 at 09:01:56AM -0700
On Tue, Aug 13, 2002 at 09:01:56AM -0700, Linus Torvalds wrote:
> > First the name souns horrible. What about spawn_thread or create_thread
> > instead? it's not our good old clone and not a lookalike, it's some
> > pthreadish monster..
>
> This one definitely isn't a pthread-specific problem. The old UNIX fork()
> semantics for <pid> returning really are fairly broken, since the notion
> of returning the pid in a local register is inherently racy for _anything_
> that wants to maintain a list of its children and needs to access the list
> in the SIGCHLD handler.
The TLS setting makes it pretty pthread-specific, though (or at least
thread-specific). Also the fn parameter makes it very different from
both clone and fork. What about spawn() if you dislike a thread in the name?
next prev parent reply other threads:[~2002-08-13 16:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-13 15:09 [patch] clone_startup(), 2.5.31-A0 Ingo Molnar
2002-08-13 15:30 ` Linus Torvalds
2002-08-13 15:44 ` Christoph Hellwig
2002-08-13 16:01 ` Linus Torvalds
2002-08-13 16:05 ` Christoph Hellwig [this message]
2002-08-13 16:20 ` Linus Torvalds
2002-08-13 18:32 ` [patch] CLONE_SETTLS, CLONE_SETTID, 2.5.31-BK Ingo Molnar
2002-08-13 18:41 ` Linus Torvalds
2002-08-13 19:09 ` Ingo Molnar
2002-08-13 19:41 ` Linus Torvalds
2002-08-13 19:41 ` Ingo Molnar
2002-08-13 19:35 ` Ingo Molnar
2002-08-15 22:38 ` [patch] complain about unknown CLONE_* flags Jamie Lokier
2002-08-16 10:17 ` Ingo Molnar
2001-11-02 5:55 ` Pavel Machek
2002-08-13 16:09 ` [patch] clone_startup(), 2.5.31-A0 Erik Andersen
2002-08-13 16:11 ` Christoph Hellwig
2002-08-13 16:32 ` David Mosberger
2002-08-13 16:44 ` John Levon
2002-08-13 19:52 ` H. Peter Anvin
2002-08-13 20:19 ` David Mosberger
2002-08-13 20:27 ` H. Peter Anvin
2002-08-13 20:52 ` David Mosberger
2002-08-13 20:57 ` H. Peter Anvin
2002-08-13 16:56 ` Ruth Ivimey-Cook
2002-08-13 17:42 ` Richard B. Johnson
2002-08-13 17:19 ` Ingo Molnar
2002-08-13 20:35 ` Kai Henningsen
2002-08-15 21:24 ` Thunder from the hill
2002-08-13 17:27 ` Ingo Molnar
2002-08-14 13:48 ` Rusty Russell
2002-08-14 18:47 ` Jamie Lokier
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=20020813170522.A12224@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.