Path: utzoo!dciem!nrcaer!sce!graham From: graham@sce.carleton.ca (Doug Graham) Newsgroups: comp.os.minix Subject: Re: An FS idea - good or bad? Message-ID: <887@sce.carleton.ca> Date: 3 Aug 90 00:33:26 GMT References: <1766@ccadfa.adfa.oz.au> <884@sce.carleton.ca> Organization: Carleton Univerity, Ottawa, Canada Lines: 18 In article peter@ficc.ferranti.com (Peter da Silva) writes: >> This finite queue size is really not a problem. Since each user task >> can have at most one I/O request pending at a time, > >I would advise against designing around this assumption, if you want to >support 1003.x later on. 1003.4 certainly requires multiple outstanding >requests, and it's handy for networking. Damn! Caught with my pants down. I rushed out and ordered a copy of 1003.4, but probably won't get it for 2 weeks or so. In the meantime, could you summarize in a paragraph or two, how it requires that a process may have multiple outstanding requests. Is this really going to be a problem? It's obvious that a process can only have a single *sychronous* request pending, and I think these are the ones that cause the problems. -- Doug.