From owner-freebsd-chat Thu Jul 15 15:14:43 1999 Delivered-To: freebsd-chat@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 6A1F615179 for ; Thu, 15 Jul 1999 15:14:42 -0700 (PDT) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Thu, 15 Jul 1999 15:13:00 -0700 From: "David Schwartz" To: "Terry Lambert" , "Tani Hosokawa" Cc: Subject: RE: Known MMAP() race conditions ... ? Date: Thu, 15 Jul 1999 15:13:00 -0700 Message-ID: <000001becf0f$33465920$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <199907151936.MAA02676@usr07.primenet.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I can't speak for David, but the process architecture I did for > the NetWare for UNIX product used multiple processes (not threads) > with a singled shared memory region for client context records, > and a shared file descriptor table. That's an excellent model to use. The biggest problem is that your processes can get blocked on disk I/O, and there's not a whole lot you can do about it. Every model has its advantages and disadvantages. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message