Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-24 Thread Andrew Morton
On Wed, 24 Jun 2009 16:52:06 -0700 (PDT) Davide Libenzi wrote: > > umm, yes please, I believe the patches should be split. And I'm still > > not seeing the justification for forcing CONFIG_EVENTFD onto all > > CONFIG_AIO users! > > Eventfd notifications became part of the AIO API (it's not even

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-24 Thread Davide Libenzi
On Wed, 24 Jun 2009, Andrew Morton wrote: > Split what? My skull? Heh :) > umm, yes please, I believe the patches should be split. And I'm still > not seeing the justification for forcing CONFIG_EVENTFD onto all > CONFIG_AIO users! Eventfd notifications became part of the AIO API (it's not e

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-24 Thread Andrew Morton
On Wed, 24 Jun 2009 15:47:47 -0700 (PDT) Davide Libenzi wrote: > On Tue, 23 Jun 2009, Andrew Morton wrote: > > > 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 o

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-24 Thread Davide Libenzi
On Tue, 23 Jun 2009, Andrew Morton wrote: > 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. Since your skull seems pretty hard to b

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Andrew Morton
On Tue, 23 Jun 2009 15:49:53 -0700 (PDT) Davide Libenzi wrote: > On Tue, 23 Jun 2009, Andrew Morton wrote: > > > On Tue, 23 Jun 2009 14:25:05 -0700 (PDT) > > Davide Libenzi wrote: > > > > > On Tue, 23 Jun 2009, Andrew Morton wrote: > > > > > > > That isn't for us to decide. Entire syscalls ca

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Davide Libenzi
On Tue, 23 Jun 2009, Andrew Morton wrote: > On Tue, 23 Jun 2009 14:25:05 -0700 (PDT) > Davide Libenzi 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 tho

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Andrew Morton
On Tue, 23 Jun 2009 14:48:51 -0700 (PDT) Davide Libenzi wrote: > > > This becomes pretty painful when the function calls other functions, for > > > which just relays the error code. > > > Should we be just documenting the error codes introduced by the function > > > code, and say that the funct

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Davide Libenzi
On Tue, 23 Jun 2009, Andrew Morton wrote: > On Tue, 23 Jun 2009 14:34:50 -0700 (PDT) > Davide Libenzi wrote: > > > On Tue, 23 Jun 2009, Andrew Morton wrote: > > > > > > Should functions be describing all the returned error codes, ala man > > > > pages? > > > > > > > > > > I think so. > > >

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Andrew Morton
On Tue, 23 Jun 2009 14:34:50 -0700 (PDT) Davide Libenzi wrote: > On Tue, 23 Jun 2009, Andrew Morton wrote: > > > > Should functions be describing all the returned error codes, ala man > > > pages? > > > > > > > I think so. > > This becomes pretty painful when the function calls other functio

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Andrew Morton
On Tue, 23 Jun 2009 14:25:05 -0700 (PDT) Davide Libenzi 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 w

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Davide Libenzi
On Tue, 23 Jun 2009, Andrew Morton wrote: > > Should functions be describing all the returned error codes, ala man pages? > > > > I think so. This becomes pretty painful when the function calls other functions, for which just relays the error code. Should we be just documenting the error codes

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Davide Libenzi
On Tue, 23 Jun 2009, Andrew Morton wrote: > > > > +struct eventfd_ctx *eventfd_ctx_get(struct eventfd_ctx *ctx) > > > > +{ > > > > + kref_get(&ctx->kref); > > > > + return ctx; > > > > +} > > > > +EXPORT_SYMBOL_GPL(eventfd_ctx_get); > > > > > > doesn't match the code. > > You appear

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Davide Libenzi
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. - Davide -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body o

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Andrew Morton
On Tue, 23 Jun 2009 14:03:22 -0700 (PDT) Davide Libenzi wrote: > On Tue, 23 Jun 2009, Andrew Morton wrote: > > > On Tue, 23 Jun 2009 12:25:36 -0700 (PDT) > > Davide Libenzi wrote: > > > > > The following patch changes the eventfd interface to de-couple the > > > eventfd > > > memory context,

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Andrew Morton
On Tue, 23 Jun 2009 13:59:07 -0700 (PDT) Davide Libenzi wrote: > On Tue, 23 Jun 2009, Andrew Morton wrote: > > > On Tue, 23 Jun 2009 12:25:36 -0700 (PDT) > > Davide Libenzi wrote: > > > > > Another cleanup this patch does, is making AIO select EVENTFD, instead of > > > adding a bunch of empty

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Davide Libenzi
On Tue, 23 Jun 2009, Andrew Morton wrote: > On Tue, 23 Jun 2009 12:25:36 -0700 (PDT) > Davide Libenzi wrote: > > > The following patch changes the eventfd interface to de-couple the eventfd > > memory context, from the file pointer instance. > > Without such change, there is no clean way to rac

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Davide Libenzi
On Tue, 23 Jun 2009, Andrew Morton wrote: > On Tue, 23 Jun 2009 12:25:36 -0700 (PDT) > Davide Libenzi wrote: > > > Another cleanup this patch does, is making AIO select EVENTFD, instead of > > adding a bunch of empty function stubs inside eventfd.h in order to > > handle the (AIO && !EVENTFD)

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Andrew Morton
On Tue, 23 Jun 2009 12:25:36 -0700 (PDT) Davide Libenzi wrote: > The following patch changes the eventfd interface to de-couple the eventfd > memory context, from the file pointer instance. > Without such change, there is no clean way to racely free handle the > POLLHUP event sent when the last

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Andrew Morton
On Tue, 23 Jun 2009 12:25:36 -0700 (PDT) Davide Libenzi wrote: > Another cleanup this patch does, is making AIO select EVENTFD, instead of > adding a bunch of empty function stubs inside eventfd.h in order to > handle the (AIO && !EVENTFD) case. Given that we're trying to squeak this patch int

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Davide Libenzi
On Tue, 23 Jun 2009, Andrew Morton wrote: > On Tue, 23 Jun 2009 12:25:36 -0700 (PDT) > Davide Libenzi wrote: > > > The following patch changes the eventfd interface to de-couple the eventfd > > memory context, from the file pointer instance. > > Without such change, there is no clean way to rac

Re: [patch] eventfd - revised interface and cleanups (2nd rev)

2009-06-23 Thread Andrew Morton
On Tue, 23 Jun 2009 12:25:36 -0700 (PDT) Davide Libenzi wrote: > The following patch changes the eventfd interface to de-couple the eventfd > memory context, from the file pointer instance. > Without such change, there is no clean way to racely free handle the > POLLHUP event sent when the last