RE: [Valgrind-users] 2.6 kernel support

[Mukund S. <mu...@sh...>]

Hi=20
Epoll_create internally uses wait locking(for threads)  to create a
system resource that can hold the descriptors on the kernel table, So
you should assume both epoll_create and epoll_ctl can block

Epoll_wait is definitely blocking. Its exactly identical to poll which
is blocking.=20

Thanks
Mukund

-----Original Message-----
From: Tom Hughes [mailto:th...@cy...]=20
Sent: Monday, January 19, 2004 2:50 PM
To: val...@li...
Subject: Re: [Valgrind-users] 2.6 kernel support

In message <Pin...@ye...>
          Nicholas Nethercote <nj...@ca...> wrote:

> On Sun, 18 Jan 2004, Jeremy Fitzhardinge wrote:
>=20
> > It should be pretty easy to do in the 2.1 tree - you just need to
add
> > PRE and POST functions to deal with the args and return vals, work
out
> > which syscalls can block, and put the entries into the table.  The
2.0
> > patch won't be much help though, because I presume most of it is to
do
> > with making epoll_* non-blocking, which isn't an issue any more.
>=20
> Are epoll_{create,ctl,wait} blocking or non-blocking?

Judging from the documentation I would think just epoll_wait is a
blocking call. I can't see any reason why either of the others should
ever block.

Tom

--=20
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Valgrind-users mailing list
Val...@li...
https://lists.sourceforge.net/lists/listinfo/valgrind-users