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 <[EMAIL PROTECTED]>
> > To: Peter Dufault <[EMAIL PROTECTED]>
> > Cc: Marc W <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
>
> > 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 [EMAIL PROTECTED]
> > with "unsubscribe freebsd-hackers" in the body of the message
> >
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
