This is the mail archive of the libc-hacker@sourceware.cygnus.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: [lia64-kernel] Re: Re: clone and clone2

To: lia64-kernel at napali dot hpl dot hp dot com
Subject: Re: [lia64-kernel] Re: Re: clone and clone2
From: Ulrich Drepper <drepper at redhat dot com>
Date: 20 Jun 2000 14:12:55 -0700
Cc: GNU C Library <libc-hacker at sourceware dot cygnus dot com>
References: <20000620110814.A27581@valinux.com> <14671.55138.129300.730776@napali.hpl.hp.com> <20000620135555.A9574@valinux.com>
Reply-To: drepper at cygnus dot com (Ulrich Drepper)

"H . J . Lu" <hjl@valinux.com> writes:

> If we all use
> 
> int clone2(int (*fn)(void *arg), void *thread_bottom, size_t stack_size, int flags, void *arg);
> 
> that is one solution. All the other CPUs who want thread_top need to use
> thread_bottom + stack_size to get thread_top in their clone.S.

This only makes sense if the kernel is actually able to limit the
growth of the stack without the user creating an artificial barrier
(as we do in the moment).

-- 
---------------.      drepper at gnu.org  ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------

References:
- clone and clone2
  - From: H . J . Lu
- Re: [lia64-kernel] Re: clone and clone2
  - From: H . J . Lu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]