On Tue, 23 Jun 2009 15:49:53 -0700 (PDT)
Davide Libenzi <davidel@xxxxxxxxxxxxxxx> wrote:
> On Tue, 23 Jun 2009, Andrew Morton wrote:
>
> > On Tue, 23 Jun 2009 14:25:05 -0700 (PDT)
> > Davide Libenzi <davidel@xxxxxxxxxxxxxxx> wrote:
> >
> > > On Tue, 23 Jun 2009, Andrew Morton wrote:
> > >
> > > > That isn't for us to decide. Entire syscalls can be disabled in config.
> > >
> > > That is not a well defined separate syscall though. It's a member/feature
> > > of the aiocb.
> >
> > I don't know what this means, really.
>
> This is the struct iocb:
>
> struct iocb {
> ...
> u_int32_t aio_resfd;
> };
>
> And the only interface to access KAIO is io_submit().
> IMO the end user perceives the KAIO functionality as the full deployment
> of the iocb struct and the io_submit() accessory.
> Can code not using eventfd work in (AIO && !EVENTFD) mode? Sure.
> It is a kinda confusing configuration from the end user POV IMO.
What's confusing about it?
Most programmers who are using AIO probably don't even know that the
eventd hookup is available. And even if they did, they might not want
to use it, to remain compatible with older kernels.
I'm still not seeing any compelling reason for unconditionally adding
kernel text which some users don't need.
Maybe there is such a reason, and it hasn't yet been beaten into my
skull. But I still think it should be done in a separate patch. One
which comes with a full description of the reasons for the change, btw.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
