From owner-freebsd-hackers  Tue Feb 27 13:49:22 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from faithful.dizzyd.com (c396142-a.lakwod2.co.home.com [24.183.233.142])
	by hub.freebsd.org (Postfix) with ESMTP id 785F937B71A
	for <freebsd-hackers@FreeBSD.ORG>; Tue, 27 Feb 2001 13:49:18 -0800 (PST)
	(envelope-from dizzyd@dizzyd.com)
Received: by faithful.dizzyd.com (Postfix, from userid 1000)
	id 05A58105F; Tue, 27 Feb 2001 14:49:16 -0700 (MST)
Date: Tue, 27 Feb 2001 14:49:16 -0700
To: Marc W <mwlist@lanfear.com>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: Where can I find out rules on blocking in threads?
Message-ID: <20010227144916.A9254@dizzyd.com>
Mail-Followup-To: Marc W <mwlist@lanfear.com>,
	freebsd-hackers@FreeBSD.ORG
References: <200102272143.NAA42419@akira.lanfear.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.12i
In-Reply-To: <200102272143.NAA42419@akira.lanfear.com>; from mwlist@lanfear.com on Tue, Feb 27, 2001 at 01:43:41PM -0800
From: dizzyd@dizzyd.com (Dave Smith)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Well, my understand (limited) of *BSD's threading systems is that
they are not truly pre-emptive -- they use a scheme similar to PTH
for forcing a single process to jump around its process space. Given
this, it doesn't suprise me that a few system calls don't yield; 
possibly because they aren't wrapped properly; or maybe can't be wrapped.

Of course, this is based on my _very_ limited knowledge... :)

D.

On Tue, Feb 27, 2001 at 01:43:41PM -0800, Marc W wrote:
> 
>     just did some more testing -- the problem does appear to be FreeBSD
> specific.  Solaris 8 and all the Linuxes I've got handy run this no
> probs.  Don't have any openbsd or netbsd to test those out ...
> 
>     I'll just #ifdef in some code for FreeBSD.  anybody know what
> #ifdef I should use before I start digging through headers?
> 
>     thanks :-)
> 
>     marc.
> 
> 
> 
> > -----------------------------
> > From:  mouss <usebsd@free.fr>
> > To:  Peter Dufault <dufault@hda.hda.com>
> > Cc:  Marc W <mwlist@lanfear.com>, freebsd-hackers@FreeBSD.ORG
> 
> > Subject:  Re: Where can I find out rules on blocking in threads?
> > Sent:  02/27/01 22:04> 
> > 
> > 
> > It seems ther's a problem here:)
> > 
> > the manpage of open states ".... disables thread rescheduling...".
> > Is this the explanation?
> > 
> > As far as I can tell, Posix requires that some function should not
> > block the process, and lists open(), fcntl(), ...
> > 
> > 
> > Are there any pthread gurus who could give us the real truth here?
> > 
> > cheers,
> > mouss
> > 
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-hackers" in the body of the message
> > 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message