From owner-freebsd-hackers Thu Jan 6 4:46:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (Postfix) with SMTP id C3A8315588 for ; Thu, 6 Jan 2000 04:46:39 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 18282 invoked from network); 6 Jan 2000 12:46:38 -0000 Received: from citadel.in.taronga.com (10.0.0.43) by mushi.in.taronga.com with SMTP; 6 Jan 2000 12:46:38 -0000 Received: by citadel.in.taronga.com (Postfix, from userid 100) id 4E64C32306; Thu, 6 Jan 2000 06:45:48 -0600 (CST) To: d_f0rce@gmx.de Subject: Re: Limited amount of variables in a multithreaded programm? X-Newsgroups: taronga.freebsd.hackers In-Reply-To: <002001bf5697$31869fe0$0201a8c0@blade> References: <20000103173027.A61058@cons.org> <20000103184233.B17710@cons.org> Organization: Cc: hackers@freebsd.org Message-Id: <20000106124548.4E64C32306@citadel.in.taronga.com> Date: Thu, 6 Jan 2000 06:45:48 -0600 (CST) From: peter@taronga.com (Peter da Silva) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >"This really is C-101 type stuff." :-) ) if you could tell me a book about >programming FreeBSD. I have Stevens "Advanced programming..." and >Haviland's "Unix System programming" but there is not much about threads >in these books. Moreover there is nothing about variable stack sizes in >threads. There's a good reason for this... multithreaded programming under UNIX is very complicated, and it should be avoided in most cases. You certainly shouldn't try writing a multithreaded program in *any* OS if you don't have a good, solid understanding of stacks and concurrency first. My preference at this point would be for you to read a good book on concurrent programming that digs into things at the instruction level. Douglas Comer's "Xinu" book is pretty good. Here's a page you should probably start your research with... http://www.faqs.org/faqs/os-research/part1/section-21.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message