Date: Tue, 1 Nov 2005 06:22:17 -0800 From: Alfred Perlstein <alfred@freebsd.org> To: David Xu <davidxu@freebsd.org> Cc: alc@freebsd.org, cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/sys aio.h signal.h signalvar.h src/sys/kern syscalls.master vfs_aio.c Message-ID: <20051101142217.GN32289@elvis.mu.org> In-Reply-To: <43655AF7.8070707@freebsd.org> References: <200510300212.j9U2CnWl089007@repoman.freebsd.org> <20051030134702.GK32289@elvis.mu.org> <43655AF7.8070707@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* David Xu <davidxu@freebsd.org> [051030 15:44] wrote: > Existing binary code needn't be recompiled, it should work as before. > if an AIO syscall needs sigevent structure, it already has a new syscall > number, and old syscalls will think passed sigevent is an osigevent. > I am open for adding pad fields to aiocb and sigevent, how many padding > do you want to add, give some diffs for us ? :-) I apologize, I didn't realize that this was actually the compat patch. I have no idea about padding, I just thought it might be a good idea, you might want to check if Sun/Apple/Linux have padding and copy that just for future expansion. But I do not have time to provide that. > > David Xu > > Alfred Perlstein wrote: > > >Does this modify the size/layout of the struct sigevent and aiocb > >to the point where apps need a recompile? If so we > >should we have compat functions for AIO? Ei, struct "osigevent" > >and "oaiocb" and corresponding compat functions for AIO? > > > >I understand that it's annoying but AIO has been an interface around > >since 4.x. > > > >Now might also be a good time to add padding to aiocb and possibly > >sigevent. > > > >-Alfred > > > > -- - Alfred Perlstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051101142217.GN32289>