Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!tut.cis.ohio-state.edu!ucsd!ogicse!plains!overby From: overby@plains.UUCP (Glen Overby) Newsgroups: comp.os.minix Subject: Re: File System blues... Summary: process threads Message-ID: <3868@plains.UUCP> Date: 24 Mar 90 00:24:49 GMT References: <14645@nigel.udel.EDU> Reply-To: overby@plains.UUCP (Glen Overby) Organization: North Dakota State University, Fargo Lines: 22 In article <14645@nigel.udel.EDU> archer%segin4.segin.fr@prime.com (Vincent Archer) writes: >In a message of 21 Mar 90 18:06, Jason Coughlin says [Continuing the discussion about the bottleneack in FS Approach 1: Kernel buffers that won't help Approach 2: Making FS handle multiple requests itself ] The "sexy new operating systems all seem to have process threads (by whatever other name you want to call it) where several "threads of execution" share the same code and DATA spaces. I would like to offer Approach 3: Approach 3: RE-Implimenting FS under a threaded system Yes, this will require kernel support. The resulting FS will be more complex since locking on all global data structures will be a necessity. -- Glen Overby uunet!plains!overby (UUCP) overby@plains (Bitnet)