I/O event notification mechanism - select() or epoll() ?
htmldeveloper at gmail.com
Wed Sep 26 11:49:23 EDT 2012
On Wed, Sep 26, 2012 at 7:49 PM, Rahul Bedarkar <rpal143 at gmail.com> wrote:
> I have to capture kernel udev events through libudev. One of API
> provides asynchronous events by reading on file descriptor. I found
> that there two ways to do that.
> 1) select call
I guessed when u called select() it will block, and so u can be very
efficient - doing nothing until necessary, but also resource being used up
- as the process is solely dedicated to listenting for event only.
> 2) epoll
> good thing is u can parallel process other stuff at the same time, if
after polling the replies from udev is not back yet. but the bad thing is
response may not be so immediate, as u may be doing something else when the
udev event comes in.
> I also found that epoll is smarter and meant to replace old select call.
> What are your thoughts on these ? Which one is better ?
> Rahul B.
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Kernelnewbies