From owner-freebsd-hackers  Mon Apr 24 14:10:26 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from mail.rdc1.sfba.home.com (ha1.rdc1.sfba.home.com [24.0.0.66])
	by hub.freebsd.org (Postfix) with ESMTP id 895DA37BBDD
	for <freebsd-hackers@FreeBSD.ORG>; Mon, 24 Apr 2000 14:10:22 -0700 (PDT)
	(envelope-from boshea@ricochet.net)
Received: from beastie.localdomain ([24.19.158.41])
          by mail.rdc1.sfba.home.com (InterMail v4.01.01.00 201-229-111)
          with ESMTP
          id <20000424211021.YUID12856.mail.rdc1.sfba.home.com@beastie.localdomain>;
          Mon, 24 Apr 2000 14:10:21 -0700
Received: (from brian@localhost)
	by beastie.localdomain (8.9.3/8.8.7) id OAA22873;
	Mon, 24 Apr 2000 14:19:57 -0700 (PDT)
	(envelope-from brian)
Date: Mon, 24 Apr 2000 14:19:57 -0700
From: "Brian O'Shea" <boshea@ricochet.net>
To: Daniel Eischen <eischen@vigrid.com>
Cc: "Brian O'Shea" <boshea@ricochet.net>,
	Jason Evans <jasone@canonware.com>, A G F Keahan <ak@freenet.co.uk>,
	freebsd-hackers@FreeBSD.ORG
Subject: Re: Multithreaded server performance
Message-ID: <20000424141957.W337@beastie.localdomain>
Reply-To: boshea@ricochet.net
Mail-Followup-To: Daniel Eischen <eischen@vigrid.com>,
	Brian O'Shea <boshea@ricochet.net>,
	Jason Evans <jasone@canonware.com>, A G F Keahan <ak@freenet.co.uk>,
	freebsd-hackers@FreeBSD.ORG
References: <20000424010315.U337@beastie.localdomain> <Pine.SUN.3.91.1000424061006.7393A-100000@pcnet1.pcnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <Pine.SUN.3.91.1000424061006.7393A-100000@pcnet1.pcnet.com>; from Daniel Eischen on Mon, Apr 24, 2000 at 06:13:53AM -0400
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Apr 24, 2000 at 06:13:53AM -0400, Daniel Eischen wrote:
> On Mon, 24 Apr 2000, Brian O'Shea wrote:
> > 
> > I was under the impression that, because user thread scheduling is done
> > in user mode, a thread that goes to sleep calling a blocking read()
> > system call will put the entire process to sleep until that read()
> > returns (and so all user threads in the process will also be blocked).
> > Is this correct?
> 
> 1. You are mistaken.

Could you elaborate?  The text that I am using [1] warns about blocking
system calls putting the process (and thus all user threads) to sleep.
This book has no FreeBSD specific information, so anything specific to
FreeBSD would be really interesting to hear.

> > 
> > Please correct me if I am wrong.
> 
> Go To 1. ;-)
> 
> -- 
> Dan Eischen
> 

Thanks,
-brian

1.  Norton, Scott J., "Thread Time", p.24, Hewlett-Packard Professional
    Books, ISBN 0-13-190067-6

-- 
Brian O'Shea
boshea@ricochet.net


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