[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0906231538280.17001@makko.or.mcafeemobile.com>
Date: Tue, 23 Jun 2009 15:49:53 -0700 (PDT)
From: Davide Libenzi <davidel@...ilserver.org>
To: Andrew Morton <akpm@...ux-foundation.org>
cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
avi@...hat.com, kvm@...r.kernel.org, ghaskins@...ell.com,
Rusty Russell <rusty@...tcorp.com.au>,
Benjamin LaHaise <bcrl@...ck.org>
Subject: Re: [patch] eventfd - revised interface and cleanups (2nd rev)
On Tue, 23 Jun 2009, Andrew Morton wrote:
> On Tue, 23 Jun 2009 14:25:05 -0700 (PDT)
> Davide Libenzi <davidel@...ilserver.org> 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.
- Davide
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists