From owner-freebsd-hackers Wed Mar 17 11:47:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id E91DF15610 for ; Wed, 17 Mar 1999 11:47:17 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA47649; Wed, 17 Mar 1999 14:45:13 -0500 (EST) Date: Wed, 17 Mar 1999 14:45:13 -0500 (EST) From: Chuck Robey To: "Daniel C. Sobral" Cc: hackers@FreeBSD.ORG Subject: Re: volatile question In-Reply-To: <36EFF74A.F42597F4@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 18 Mar 1999, Daniel C. Sobral wrote: > >From aio.h: > > typedef struct aiocb { > int aio_fildes; /* File descriptor */ > off_t aio_offset; /* File offset for I/O */ > volatile void *aio_buf; /* I/O buffer in process > space */ > ^^^^^^^^^^^^^^^^^^^^^^^ > size_t aio_nbytes; /* Number of bytes for I/O > */ > struct sigevent aio_sigevent; /* Signal to deliver */ > int aio_lio_opcode; /* LIO opcode */ > int aio_reqprio; /* Request priority -- > ignored */ > struct __aiocb_private _aiocb_private; > } aiocb_t; > > Is the volatile keyword in the right position? Shouldn't it be void* > volatile aio_buf? H&S pages 74-75: that code is right. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message