From owner-freebsd-arch Wed Nov 3 7:26: 6 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id E968114D1B for ; Wed, 3 Nov 1999 07:26:03 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id QAA12297 for ; Wed, 3 Nov 1999 16:24:46 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA87424 for freebsd-arch@freebsd.org; Wed, 3 Nov 1999 16:24:45 +0100 (MET) Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 65A8814D1B for ; Wed, 3 Nov 1999 07:24:01 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id IAA11971; Wed, 3 Nov 1999 08:23:36 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id IAA08555; Wed, 3 Nov 1999 08:23:35 -0700 Date: Wed, 3 Nov 1999 08:23:35 -0700 Message-Id: <199911031523.IAA08555@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Daniel M. Eischen" Cc: Nate Williams , Julian Elischer , freebsd-arch@freebsd.org Subject: Re: Threads models and FreeBSD. (Next Step) In-Reply-To: <381F85F2.BF6D5A2@vigrid.com> References: <19991102173736.9E34E1FCD@io.yi.org> <199911022319.QAA26200@mt.sri.com> <381F78AF.D5073BFB@vigrid.com> <199911030016.RAA26726@mt.sri.com> <381F85F2.BF6D5A2@vigrid.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The idea of being 'too flexible' scares me. Writing correct threaded > > code is hard, when you start throwing in the complexity of determining > > thread scheduler models, types of threads to create, etc..., and all of > > a sudden multi-process solutions start to look pretty good. > > Well, stick with what you know then ;-) And also make sure whatever > we do gets sufficiently documented! You're missing my point. Writing correct threaded code is hard, and if we make it too difficult, it will have *very* little effect on the userbase, since very few people will be able to write code for FreeBSD. Highly motivated individuals will be able to write code, but if we come up with a very complicated design that requires lots of extra work, very few people will be able to use the new threaded features of FreeBSD. My plea is to keep is simple. KISS rules here, and although flexibility is a grand goal, KISS should always win out. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message