This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Ulrich- This answers an old question about the aiocbp struct. -- Mark S. Brown bmark@us.ibm.com Senior Technical Staff Member 512.838.3926 T/L678.3926 AIX and Linux Technologies Mark Brown/Austin/IBM IBM Corporation, Austin, Texas ---------- > From: Andrew Josey <ajosey@rdg.opengroup.org> > Reply-To: ajosey@rdg.opengroup.org (Andrew Josey) > Date: Thu, 15 Mar 2001 08:52:00 GMT > To: m.brown@opengroup.org > Cc: stds-pasc-ieee-officers@ieee.org,sc22wg15@dkuug.dk > Subject: (wg15tag 2582) (SC22WG15.1583) Finalised PASC 1003.1 Interpretation > #118 > Resent-From: wg15tag@opengroup.org > Resent-To: wg15tag@opengroup.org > Resent-Date: 15 Mar 2001 08:56:53 -0000 > > > To: Mr. Brown > From: Andrew Josey, PASC Interpretations Functional Chair > Reference: PASC 1003.1 #118 > > > Dear Mr. Brown > > Enclosed is the official response for your request for an interpretation > of IEEE Standard 1003.1. > > This response was developed and approved by the members of the 1003.1 > Interpretations Committee. > > To obtain an understanding of the PASC Guidelines for interpretations > and their classifications please read > http://www.pasc.org/interps/ > > Please can you confirm receipt of this electronic mail message > within ten working days, please carbon copy your response to the IEEE > (stds-pasc-ieee-officers@ieee.org) > > Sincerely, > > > Andrew Josey > PASC Functional Chair Interpretations > > Enclosures > > > Cc: IEEE PASC Officers, SC22 WG15 > > > > > > _____________________________________________________________________________ > Notice: This is an unapproved draft PASC interpretation. Use at > your own risk. Please direct any questions to a.josey@pasc.org > > > _____________________________________________________________________________ > PASC Interpretation reference > 1003.1-96 #118 > > _____________________________________________________________________________ > > Interpretation Number: XXXX > Topic: aio_fsync > Relevant Sections: 6.7.9.2 Lines 1252-1265 > > > PASC Interpretation Request: > ---------------------------- > > From: Mark S. Brown > Date: 2000 Oct 23 > > ------------------------------------------------------------------------ > > 7 Defect Report concerning (number and title of International Standard > or DIS final text, if applicable): > > IEEE Std 1003.1-1996 (incorporates 1003.1-1990, 1003.1b-1993, 1003.1c-1995, > 1003.1i-1995) (ISO 9945-1:1996) > > ------------------------------------------------------------------------ > > 8 Qualifier (e.g. error, omission, clarification required): > > 3 > > Error=1 , Omission=2, Clarification=3 > > ------------------------------------------------------------------------ > > 9 References in document (e.g. page, clause, figure, and/or table > numbers): > > Sec 6.7.9.2 Lines 1252-1265 > > ------------------------------------------------------------------------ > > 10 Nature of defect (complete, concise explanation of the perceived > problem): > > > This paragraph describes the aiocbp structure and its uses, in > apparently general terms. It is unclear whether this paragraph > is meant for use in all of the APIs in which aiocbp is used, > or only aio_fsync(). What is unclear in particular, are the > sentences, > "The aio_sigevent member shall determine the asynchronous > notification to occur as specified in 3.3.1.2 when all operations > have achieved synchronous I/O completion. All other members of the > structure referenced by aiocbp are ignored." > > 1. Does this apply to all of the APIs? It would make implementation > pretty difficult if we can't use the rest of the structure. > > 2. Does this sentence apply only to aio_fsync(), since the paragraph > is in 6.7.9 and not in a more general section? > > 3. Does it apply to aio_error() and aio_return()? > > ------------------------------------------------------------------------ > > 11 Solution proposed by the submitter (optional): > > > > > ------------------------------------------------------------------------ > > > > Interpretation response > ------------------------ > No this sentence applies only to aio_fsync(). > > Rationale > ------------- > For this function only, only the aio_fildes and aio_sigevent fields > of the AIO control block are used; the rest are ignored since no > seeking , (specific) writing, or reading takes place in this operation. > > > Forwarded to Interpretations group: 31 Oct 2000 > Proposed resolution: 15 Feb 2001 > Finalised: 15 Mar 2001 > > > ----- > Andrew Josey The Open Group > PASC FC Interpretations Apex Plaza,Forbury Road, > Email: a.josey@opengroup.org Reading,Berks.RG1 1AX,England > Tel: +44 118 9508311 ext 2250 Fax: +44 118 9500110 > > PASC Interpretations Web Site: http://www.pasc.org/interps/ > or http://pasc.opengroup.org/interps/ > >
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |