[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060823131130.GA29056@2ka.mipt.ru>
Date: Wed, 23 Aug 2006 17:11:31 +0400
From: Evgeniy Polyakov <johnpol@....mipt.ru>
To: Jari Sundell <sundell.software@...il.com>
Cc: David Miller <davem@...emloft.net>, kuznet@....inr.ac.ru,
nmiell@...cast.net, linux-kernel@...r.kernel.org,
drepper@...hat.com, akpm@...l.org, netdev@...r.kernel.org,
zach.brown@...cle.com, hch@...radead.org
Subject: Re: [take12 0/3] kevent: Generic event handling mechanism.
On Wed, Aug 23, 2006 at 02:55:47PM +0200, Jari Sundell (sundell.software@...il.com) wrote:
> On 8/23/06, Evgeniy Polyakov <johnpol@....mipt.ru> 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.
>
> 7.18.1.4 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?
stdint.h
/* Types for `void *' pointers. */
#if __WORDSIZE == 64
# ifndef __intptr_t_defined
typedef long int intptr_t;
# define __intptr_t_defined
# endif
typedef unsigned long int uintptr_t;
#else
# ifndef __intptr_t_defined
typedef int intptr_t;
# define __intptr_t_defined
# endif
typedef unsigned int uintptr_t;
#endif
which means that with 32bit userspace it will be equal to 32bit only.
> I'm unable to see anything specific about AIO in your kevent patch
> that these modifications wouldn't support.
I was asked to postpone AIO stuff for now, you can find it in previous
patchsets sent about week or two ago.
> Rakshasa
--
Evgeniy Polyakov
-
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