All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave McCracken <dmccr@us.ibm.com>
To: george anzinger <george@mvista.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [RFC] POSIX personality
Date: Tue, 21 May 2002 16:21:38 -0500	[thread overview]
Message-ID: <79630000.1022016098@baldur.austin.ibm.com> (raw)
In-Reply-To: <3CEAB85D.1532F5A2@mvista.com>


--On Tuesday, May 21, 2002 02:13:01 PM -0700 george anzinger
<george@mvista.com> wrote:

> What you are proposing seem a bit vague.  I think that
> CLONE_THREAD should group all the thread related stuff under
> the one flag.  IMHO POSIX compatibility should not be off in
> the corner as a step child, but rather should be the norm. 
> The CLONE_THREAD flag would indicate to fork that it should
> create a POSIX thread and set up the needed shared stuff.  I
> rather image this to be a structure that each task_struct
> points to, possibly with a usage count (but that is a
> detail).  Each thread_struct would point to such a
> structure, but processes that are not threaded would not be
> sharing this area with other threads.

That's a possibility I've considered, but I gather most of the kernel
community would prefer to see each resource have its own flag to clone() so
applications can pick and choose which ones to share.  I'm guessing that in
most cases multithreaded apps will choose all flags.

Dave McCracken

======================================================================
Dave McCracken          IBM Linux Base Kernel Team      1-512-838-3059
dmccr@us.ibm.com                                        T/L   678-3059


  reply	other threads:[~2002-05-21 21:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 20:27 [RFC] POSIX personality Dave McCracken
2002-05-21 20:52 ` Linus Torvalds
2002-05-21 20:56   ` Dave McCracken
2002-05-23 14:10   ` Bill Davidsen
2002-05-23 17:09     ` Linus Torvalds
2002-05-25  0:02       ` jw schultz
2002-05-25  0:38         ` Alan Cox
2002-06-05 13:26         ` Bill Davidsen
2002-05-21 21:13 ` george anzinger
2002-05-21 21:21   ` Dave McCracken [this message]
     [not found] <Pine.LNX.4.33.0205211349100.3073-100000@penguin.transmeta.com.suse.lists.linux.kernel>
     [not found] ` <72190000.1022014608@baldur.austin.ibm.com.suse.lists.linux.kernel>
2002-05-21 21:35   ` Andi Kleen
2002-05-21 23:08     ` Linus Torvalds
2002-05-22 14:19       ` Dave McCracken
2002-05-28 17:26         ` Michael Sinz
2002-05-28 17:31           ` Dave McCracken
     [not found] <187597808@toto.iv>
2002-05-21 23:55 ` Peter Chubb

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=79630000.1022016098@baldur.austin.ibm.com \
    --to=dmccr@us.ibm.com \
    --cc=george@mvista.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 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.