From owner-freebsd-arch@FreeBSD.ORG  Mon May  5 07:07:58 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D34B937B401
	for <freebsd-arch@freebsd.org>; Mon,  5 May 2003 07:07:58 -0700 (PDT)
Received: from park.rambler.ru (park.rambler.ru [81.19.64.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4E3E743F75
	for <freebsd-arch@freebsd.org>; Mon,  5 May 2003 07:07:57 -0700 (PDT)
	(envelope-from is@rambler-co.ru)
Received: from is.park.rambler.ru (is.park.rambler.ru [81.19.64.102])
	by park.rambler.ru (8.12.6/8.12.6) with ESMTP id h45E7tmF061397;
	Mon, 5 May 2003 18:07:55 +0400 (MSD)
Date: Mon, 5 May 2003 18:07:55 +0400 (MSD)
From: Igor Sysoev <is@rambler-co.ru>
X-Sender: is@is
To: Terry Lambert <tlambert2@mindspring.com>
In-Reply-To: <3EB66C92.304110A4@mindspring.com>
Message-ID: <Pine.BSF.4.21.0305051756330.62854-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-arch@freebsd.org
Subject: Re: rfork(RFPROC|RFMEM)
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 May 2003 14:07:59 -0000

On Mon, 5 May 2003, Terry Lambert wrote:

> Igor Sysoev wrote:
> > As stated in http://www.freebsd.org/cgi/query-pr.cgi?pr=50923
> > rfork(RFPROC|RFMEM) in 4.8-STABLE and 5.0-CURRENT requires RFTHREAD flag
> > but it is not even mentioned in man page.
> 
> This makes the stack glue implicit.  You can also use explicit
> stack glue.  Most people using the RFPROC flag use explicit
> stack glue, i.e. we carry arounbd our own assembly language
> trampoline code for stack setup that John Dyson originally
> wrote.  I think wanting RFPROC to act like Linux's "clone"
> system call is probably wrong.

What is stack glue ?
I use rfork_thread(3) wrapper that allows to setup another stack for
rfork()ed process.

What RFTHREAD flag does ?
By the way linuxthreads port always uses RFTHREAD flag.


Igor Sysoev
http://sysoev.ru/en/