Re: [take12 0/3] kevent: Generic event handling mechanism.
From: Jari Sundell
Date: Wed Aug 23 2006 - 08:53:16 EST
On 8/23/06, Evgeniy Polyakov <johnpol@xxxxxxxxxxx> wrote:
We still do not know what uintptr_t is, and it looks like it is a pointer,
which is forbidden. Those numbers are not enough to make network AIO.
And actually is not compatible with kqueue already, so you will need to
write your own parser to convert your parameters into above structure.
188.8.131.52 Integertypes capable of holding object pointers
"1 The following type designates a signed integer type with the
property that any valid
pointer to void can be converted to this type, then converted back to
pointer to void,
and the result will compare equal to the original pointer:"
Dunno if this means that x86-64 needs yet another typedef, or if using
long for intptr_t is incorrect. But assuming a different integer type
was used instead of intptr_t, that is known to be able to hold a
pointer, would there still be any problems?
I'm unable to see anything specific about AIO in your kevent patch
that these modifications wouldn't support.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/