Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!munnari.oz.au!metro!ipso!runxtsa!brucee
From: brucee@runxtsa.runx.oz.au (Bruce Evans)
Newsgroups: comp.os.minix
Subject: Re: FS - What way to go?
Message-ID: <2069@runxtsa.runx.oz.au>
Date: 28 Jul 90 18:41:02 GMT
References: <25468@nigel.udel.EDU>
Organization: RUNX Unix Timeshare.  Sydney, Australia.
Lines: 19

In article <25468@nigel.udel.EDU> ZT0009%DMSWWU1C.BITNET@cunyvm.cuny.edu (Kai Henningsen) writes:

>Also, the disk driver would have to use coroutines as well - probably two:
>One to do actual I/O, the other to wait for messages and build sorted
>lists of requests.

This is not essential. Better make FS multitasking first. The sorting now done
done by FS works fairly well, and sending i/o vectors is more efficient than a
lot of little messages.

>Of course, as I said above, the kernel messaging scheme would need a major
>overhaul. We might as well split it from user-to-kernel-messaging completely.

If you change almost everything to use threads, it would hardly be worth
keeping the current task structure, and the system would no longer be Minix.
-- 
Bruce Evans
Internet: brucee@runxtsa.runx.oz.au    UUCP: uunet!runxtsa.runx.oz.au!brucee
(My other address (evans@ditsyda.oz.au) no longer works)