Re: aio_read() oddness
I'd asked myself the same thing. In code that uses it I have to do an #ifdef FreeBSD. My guess was that it was because it is more conformant with the structure name and no one of consequence noticed because the underlying functionality is not really there. -Kip = For RAIDANT status see: http://cranford.eng.netapp.com:8080/cgi-bin/ant4/index.cgi To submit RAIDANT test descriptions go to: http://web.netapp.com/engineering/projects/raidv2/testing/ Ontap on the web: http://web.netapp.com/engineering/projects/raidv2/testing/global/ On Wed, 6 Mar 2002, Tony Arcieri wrote: > Note: Please cc replies to me as I'm not currently subscribed. > > Kip Macy <[EMAIL PROTECTED]> wrote: > > > FreeBSD does not support queued signals (part of RT Posix) which is > > required for this. > > > >-Kip > > I guess I'll have to take a look at kqueues then. On a similar note, I > was wondering why FreeBSD declares the sigval union with the following > members: > > int sigval_int; > void*sigval_ptr; > > when other operating systems (namely Solaris and Irix) declare it with > something like: > > int32_t sival_int; > caddr32_t sival_ptr; > > The difference I'm refering to is the member names, sival versus sigval. > (The above snippet is from Solaris's sys/siginfo.h) > > Is there some reason I don't know about for FreeBSD doing it differently? > > Tony Arcieri > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: aio_read() oddness
Note: Please cc replies to me as I'm not currently subscribed. Kip Macy <[EMAIL PROTECTED]> wrote: > FreeBSD does not support queued signals (part of RT Posix) which is > required for this. > >-Kip I guess I'll have to take a look at kqueues then. On a similar note, I was wondering why FreeBSD declares the sigval union with the following members: int sigval_int; void*sigval_ptr; when other operating systems (namely Solaris and Irix) declare it with something like: int32_t sival_int; caddr32_t sival_ptr; The difference I'm refering to is the member names, sival versus sigval. (The above snippet is from Solaris's sys/siginfo.h) Is there some reason I don't know about for FreeBSD doing it differently? Tony Arcieri To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: aio_read() oddness
FreeBSD does not support queued signals (part of RT Posix) which is required for this. -Kip = For RAIDANT status see: http://cranford.eng.netapp.com:8080/cgi-bin/ant4/index.cgi To submit RAIDANT test descriptions go to: http://web.netapp.com/engineering/projects/raidv2/testing/ Ontap on the web: http://web.netapp.com/engineering/projects/raidv2/testing/global/ On Wed, 6 Mar 2002, Peter J. Blok wrote: > On Wednesday 06 March 2002 07:03, Tony Arcieri wrote: > > I'm not currently subscribed to this list, so please cc replies to me. > > > > I was playing around with aio_read() and ran into some seemingly aberrant > > behavior, although not with aio_read() itself, but the resulting signal. > > Within struct aiocb I was setting: > > > > aio_sigevent.sigev_notify = SIGEV_SIGNAL; > > aio_sigevent.sigev_value.sigval_int = 42; > > iocb.aio_sigevent.sigev_signo = SIGUSR1; > > > > Then in the sigaction structure: > > sa_flags = SA_SIGINFO; > > > > Upon completion of the requested read, a signal is sent. Within the > > siginfo structure, si_signo is set properly. > > > > However, si_value.sigval_int is zero. Is this just not implemented > > completely yet or am I missing something? > I have a set of aio test tools and it indeed seems it is not implemenented. I > am getting a zero value too. > > > > Tony Arcieri > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: aio_read() oddness
On Wednesday 06 March 2002 07:03, Tony Arcieri wrote: > I'm not currently subscribed to this list, so please cc replies to me. > > I was playing around with aio_read() and ran into some seemingly aberrant > behavior, although not with aio_read() itself, but the resulting signal. > Within struct aiocb I was setting: > > aio_sigevent.sigev_notify = SIGEV_SIGNAL; > aio_sigevent.sigev_value.sigval_int = 42; > iocb.aio_sigevent.sigev_signo = SIGUSR1; > > Then in the sigaction structure: > sa_flags = SA_SIGINFO; > > Upon completion of the requested read, a signal is sent. Within the > siginfo structure, si_signo is set properly. > > However, si_value.sigval_int is zero. Is this just not implemented > completely yet or am I missing something? I have a set of aio test tools and it indeed seems it is not implemenented. I am getting a zero value too. > > Tony Arcieri > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
aio_read() oddness
I'm not currently subscribed to this list, so please cc replies to me. I was playing around with aio_read() and ran into some seemingly aberrant behavior, although not with aio_read() itself, but the resulting signal. Within struct aiocb I was setting: aio_sigevent.sigev_notify = SIGEV_SIGNAL; aio_sigevent.sigev_value.sigval_int = 42; iocb.aio_sigevent.sigev_signo = SIGUSR1; Then in the sigaction structure: sa_flags = SA_SIGINFO; Upon completion of the requested read, a signal is sent. Within the siginfo structure, si_signo is set properly. However, si_value.sigval_int is zero. Is this just not implemented completely yet or am I missing something? Tony Arcieri To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
