home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!news.service.uci.edu!unogate!mvb.saic.com!macro32
- From: "Frank J. Nagy:VAX Wizard&Loose Cannon" <NAGY@FNDCD.BITNET>
- Newsgroups: vmsnet.internals
- Subject: Re: Call for partly-baked ideas: $QIO replacement?
- Message-ID: <9726164@MVB.SAIC.COM>
- Date: Thu, 17 Dec 1992 07:11 CST
- Organization: Macro32<==>Vmsnet.Internals Gateway
- X-Gateway-Source-Info: Mailing List
- Lines: 25
-
- In article <1992Dec16.113301.977@cmkrnl.com>, jeh@cmkrnl.com writes:
- > Are you happy with the $QIO system service? [...]
-
- While I don't have any ideas as to replacements for $QIO, I have
- a couple of points to make about any I/O system.
-
- The first is that the basic I/O system should (or must?) provide
- asynchronous I/O services to the user. While it is true that at
- its heart, the kernel I/O system is asynchronous, the idea here is
- to provide those capabilities to the user. This is true of VMS $QIO
- with event flags and/or completion ASTs and is a powerful feature for
- constructing high performance (both fast and rapid response) servers
- which run on multi-user systems. In addition, one can always create
- a synchronous I/O library on an asynchronous base (but the other way
- around gets pretty hairy).
-
- Oops, now I've forgotten my other points. Another time then...
-
- = Dr. Frank J. Nagy "VAX Guru & Wizard, Loose Cannon" {{Group Leader!}}
- = Fermilab Computing Division/Distributed Computing Dept/Special Projects Grp
- = HEPnet/SPAN: FNDCD::NAGY (43123::NAGY) or FNAL::NAGY (43009::NAGY)
- = Internet: NAGY@FNAL.FNAL.GOV = BitNet: NAGY@FNAL
- = -or- NAGY@FNDCD.FNAL.GOV -or- NAGY@FNDCD
- = USnail: Fermilab POB 500 MS/234 Batavia, IL 60510
-
-