public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Boehm, Hans" <hans_boehm@hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] _clone system call
Date: Tue, 28 May 2002 22:52:32 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905604@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905602@msgid-missing>

The _clone function can't be usefully implemented on Itanium, since it doesn't provide for a place to put the register stack.  If you really have to, use __clone2 instead.  Its interface is identical to __clone except that an additional argument is added after the stack base; it's the stack size.

Under most circumstances, pthread_create is greatly preferred to either __clone or __clone2.  The problem with calling __clone or __clone2 directly is that things are unlikely to work correctly if another library routine also want to create a thread or needs to provide for mutual exclusion.

Hans

> -----Original Message-----
> From: Wedum, Patricia [mailto:patricia.wedum@intel.com]
> Sent: Tuesday, May 28, 2002 3:34 PM
> To: 'linux-ia64@linuxia64.org'
> Subject: [Linux-ia64] _clone system call
> 
> 
> 
> 
> I have been unable to find an implementation for the _clone 
> function call
> (calls clone2 system call).
> 
> Does anyone know if it exists for ia64, I found an i386 
> implementation in
> the latest glibc? I see the
> pthread library making a call to clone2 but it is not using the _clone
> interface.
> 
> Thank You
> Patricia
> 
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
> 


      reply	other threads:[~2002-05-28 22:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 22:33 [Linux-ia64] _clone system call Wedum, Patricia
2002-05-28 22:52 ` Boehm, Hans [this message]

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=marc-linux-ia64-105590701905604@msgid-missing \
    --to=hans_boehm@hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /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