From: Davide Libenzi <davidel@xmailserver.org>
To: Vadim Lobanov <vlobanov@speakeasy.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] epoll
Date: Fri, 23 Sep 2005 10:31:05 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0509231027300.10222@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0509222254390.5524@shell2.speakeasy.net>
On Thu, 22 Sep 2005, Vadim Lobanov wrote:
> On Thu, 22 Sep 2005, Davide Libenzi wrote:
>
>> This born from the initial epoll implementation, that was using the size
>> parameter to size the hash. Since now epoll uses rbtrees, the parameter is
>> no more used. Changing the API to remove it, and break userspace, was/is
>> not a good idea.
>>
>
> Any thoughts on allowing a size of '0'?
We would need to change man pages for that, and this IMHO w/out a strong
reason of doing so.
>> Yes, it is nicer if epoll behaves like poll. (*)
>>
>
> No patch needed from me here, then?
No need thx. I'll be sending the one-liner to the list right now.
>>> 3. Wakeup
>>> As determined by testing with userland code, the sys_tgkill() and
>>> sys_tkill() functions currently will NOT wake up a sleeping
>>> epoll_wait(). Effectively, this means that epoll_wait() is NOT a pthread
>>> cancellation point. There are two potential issues with this:
>>> - epoll_wait() meets the unofficial(?) definition of a "system call that
>>> may block".
>>> - epoll_wait() behaves differently from poll() and friends.
>>
>> The epoll_wait() wait loop is the standard one that even poll() uses (prep
>> wait, make interruptible, test signals, sched timeo). So if poll() is woke
>> up, so should epoll_wait(). A minimal code snippet that proves poll()
>> behing woke up, and epoll_wait() not, would help.
>>
>
> Certainly. :-) See end of email for sample program.
I'm afraid you need to bug the glibc guys, since I think they wrap
sys_poll(). Try the test program below, when defining _X_, that makes it
call sys_poll() directly. It will have the same epoll_wait() behaviour.
- Davide
#include <sys/epoll.h>
#include <sys/poll.h>
#include <pthread.h>
#include <stdio.h>
#include <linux/unistd.h>
#include <errno.h>
#include <unistd.h>
#define __NR_xpoll __NR_poll
#define __sys_xpoll(ufds, nfds, timeout) _syscall3(int, xpoll, struct pollfd *, ufds, \
unsigned int, nfds, long, timeout)
__sys_xpoll(ufds, nfds, timeout);
void * run (int * fd) {
struct epoll_event result;
printf("Wait forever while polling.\n");
#if defined(_E_)
epoll_wait(*fd, &result, 1, -1);
#elif defined(_X_)
xpoll(NULL, 0, -1);
#else
poll(NULL, 0, -1);
#endif
printf("Uhoh! Something is borked!\n");
return NULL;
}
int main (void) {
int events;
pthread_t thread;
#if defined(_E_)
events = epoll_create(1);
#endif
pthread_create(&thread, NULL, (void * (*) (void *))run, &events);
getchar();
printf("Try to kill the thread.\n");
pthread_cancel(thread);
pthread_join(thread, NULL);
printf("Success.\n");
#if defined(_E_)
close(events);
#endif
return 0;
}
next prev parent reply other threads:[~2005-09-23 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 3:12 Vadim Lobanov
2005-09-23 5:34 ` Davide Libenzi
2005-09-23 6:00 ` Vadim Lobanov
2005-09-23 17:31 ` Davide Libenzi [this message]
2005-09-23 18:39 ` Vadim Lobanov
2005-09-23 19:09 ` Davide Libenzi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0509231027300.10222@localhost.localdomain \
--to=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vlobanov@speakeasy.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®