From ljm@SLAC.Stanford.EDU Thu May 23 00:08:38 1996 Received: from serv05.slac.stanford.edu (SERV05.SLAC.Stanford.EDU [134.79.16.135]) by dkuug.dk (8.6.12/8.6.12) with ESMTP id AAA24358 for ; Thu, 23 May 1996 00:08:32 +0200 Received: from [134.79.128.74] ("port 2059"@MOZART.SLAC.Stanford.EDU) by SERV05.SLAC.STANFORD.EDU (PMDF V5.0-6 #10979) id <01I50E79CTW2001EI6@SERV05.SLAC.STANFORD.EDU> for SC22WG5@dkuug.dk; Wed, 22 May 1996 15:07:13 -0800 (PST) Date: Wed, 22 May 1996 15:07:13 -0800 From: ljm@SLAC.Stanford.EDU (Leonard J. Moss) Subject: Re: (SC22WG5.1089) X3J3 work in progress on asynch I/O X-Sender: ljm@popserv.slac.stanford.edu To: SC22WG5@dkuug.dk (SC22/WG5 Mailing List) Message-id: X-Envelope-to: SC22WG5@dkuug.dk MIME-version: 1.0 Content-type: text/plain; charset="us-ascii" Content-transfer-encoding: 7BIT At 12:38 5/22/1996, Stan Whitlock DTN 381-2011 ZKO2-3/N30 To: X3J3 X3J3/96-040r1 >From: /jor (bleikamp) page 1 of 2 >Subject: ASYNC I/O : Requirements for F2000 > >... > - The READ/WRITE statements will optionally return some sort of > "handle", which uniquely identifies a particular I/O request. > The WAIT mechanism will allow WAITing for a particular request > via the "handle", AND, alternatively, allow WAITing for all requests > for a user specified unit to complete, without specify any "handles". Has there been any discussion of the possibility of WAITing for the OR of several or all requests, with some way to identify the handle(s) of the completed request(s)? This would allow a program to issue, for example, several independent reads then start processing the first one to complete. -- Leonard J. Moss | My views don't necessarily Stanford Linear Accelerator Center | reflect those of SLAC, MS 97; P.O. Box 4349; Stanford, CA 94309 | Stanford or the DOE