From owner-freebsd-newbies Thu Jul 1 4:34:11 1999 Delivered-To: freebsd-newbies@freebsd.org Received: from gw.caamora.com.au (jonath5.lnk.telstra.net [139.130.41.237]) by hub.freebsd.org (Postfix) with ESMTP id 322F914DBE for ; Thu, 1 Jul 1999 04:34:02 -0700 (PDT) (envelope-from jon@gw.caamora.com.au) Received: (from jon@localhost) by gw.caamora.com.au (8.8.8/8.8.8) id VAA15876; Thu, 1 Jul 1999 21:31:11 +1000 (EST) (envelope-from jon) Message-ID: <19990701213110.F14477@caamora.com.au> Date: Thu, 1 Jul 1999 21:31:10 +1000 From: jonathan michaels To: Ulairi , lnb@cybertouch.org Cc: Newbies Subject: Re: reentrant kernel Mail-Followup-To: Ulairi , lnb@cybertouch.org, Newbies References: <199907010116.VAA94928@freedom.cybertouch.org> <000901bec38e$b4d84fc0$29c4edd0@ulairi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <000901bec38e$b4d84fc0$29c4edd0@ulairi>; from Ulairi on Wed, Jun 30, 1999 at 11:55:29PM -0700 X-Operating-System: FreeBSD gw.caamora.com.au 2.2.7-RELEASE i386 X-Mood: i'm alive, if it counts Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Sender: owner-freebsd-newbies@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jun 30, 1999 at 11:55:29PM -0700, Ulairi wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > A re-entrant kernel is a kernel whose functions are designed to run on > multiple CPUs at once. because this is wrong ... all that you say that is based upon this is in error. back in 1978-82 we were writing re-entrant code fro system tools and real world applications in os9, not just for teh unix like microware os9 kernel .. on single unit motorola mc6800 processor systems. i don't remember why the intel chips have such real troubel with kernel reentracy, could be the sloppy chip design or teh worse assembler language .. when compared to teh clean and relatively efficient assmebler for motorola silicon. i'll digup some notes or colleauges and get back to you > Simplified, here's the thing: when kernel's > threads make system calls (request resources, whatever), they will > block other threads from getting the same resources until the first > thread has finished. ipc - interprocess communications or messaging has little if anyting to do with code fragment re-entrancy. its more like the old argument concerning monolithic kernel design or micro kernel, this is where all teh subsystems of a kernel are built as dicrete entities that can be mixed and packed to build the required ... well something like that, i don't have my microware documentation any more and its been so long ago. regards jonathan -- =============================================================================== Jonathan Michaels PO Box 144, Rosebery, NSW 1445 Australia =========================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-newbies" in the body of the message