shore@mtxinu.COM (Melinda Shore) (03/01/91)
In article <8apb02oe05gc01@JUTS.ccc.amdahl.com> cpm00@DUTS.ccc.amdahl.com (Craig P McLaughlin) writes: >How would one go about adapting a single-threaded filesystem to a UNIX-style >multi-threaded filesystem? Just what kind of changes are going to be needed? Encore has already done this, and done it well. They've also published the details in numerous papers. Look through some recent Usenix proceedings. -- Software longa, hardware brevis Melinda Shore shore@mtxinu.com mt Xinu ..!uunet!mtxinu.com!shore
fkittred@bbn.com (Fletcher Kittredge) (03/01/91)
In article <1991Mar1.070700.1122@mtxinu.COM> shore@mtxinu.com (Melinda Shore) writes: >In article <8apb02oe05gc01@JUTS.ccc.amdahl.com> cpm00@DUTS.ccc.amdahl.com (Craig P McLaughlin) writes: >>How would one go about adapting a single-threaded filesystem to a UNIX-style >>multi-threaded filesystem? Just what kind of changes are going to be needed? > >Encore has already done this, and done it well. They've also published >the details in numerous papers. Look through some recent Usenix proceedings. >-- And through "Computing Systems", "Mach/4.3BSD: a Conservative Approach to Parallelization" Joseph Boykin and Alan Langerman Computing Systems, Winter 1990 > Software longa, hardware brevis >Melinda Shore shore@mtxinu.com >mt Xinu ..!uunet!mtxinu.com!shore regards, fletcher Fletcher Kittredge Platforms and Tools Group, BBN Software Products 10 Fawcett Street, Cambridge, MA. 02138 617-873-3465 / fkittred@bbn.com / fkittred@das.harvard.edu
guy@auspex.auspex.com (Guy Harris) (03/03/91)
>>How would one go about adapting a single-threaded filesystem to a UNIX-style >>multi-threaded filesystem? Just what kind of changes are going to be needed? > >Encore has already done this, and done it well. Encore's already done *something*; whether it's "this" or not is another question. I.e., from his reference to "multi-threaded filesystem(s)" as being "UNIX-style", I assumed he considered "UNIX-style filesystem(s)" as being intrinsically "multi-threaded", perhaps meaning that multiple UNIX-style processes could access them. Encore took a file system that was already "UNIX-style", and made it work in a multiprocessor kernel with thread support. Methinks the original poster should indicate precisely what he meant by "adapting a single-threaded filesystem to a UNIX-style multi-threaded filesytem".