mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davide Libenzi <davidel@xmailserver.org>
To: Mark Hamblin <MarkHamblin@cox.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.46: epoll ep_insert doesn't wake waiters if events exist
Date: Fri, 8 Nov 2002 09:43:46 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0211080938081.1768-100000@blue1.dev.mcafeelabs.com> (raw)
In-Reply-To: <014f01c2873e$794089b0$0200a8c0@cirilium.com>

On Fri, 8 Nov 2002, Mark Hamblin wrote:

> Looking at the documentation at
> http://www.xmailserver.org/linux-patches/epoll_wait.txt, I noticed that the
> description for epoll_wait states:  "On success, epoll_wait(2) returns the
> number of file descriptors ready for the requested I/O."  My question is if
> I have, for example, 1000 sockets registered with epoll and 100 of them have
> received data and I call epoll_wait with max_events set to 10, will
> epoll_wait return 10 or 100?  Furthermore, does the edge-triggered nature of
> epoll "eat the edge" for the other 90 sockets even though they didn't get
> returned?  Finally, if those 10 sockets get more data before I call
> epoll_wait with max_events = 10 again, will those same 10 sockets get
> returned?

epoll will return 10 and the remaining 90 will remain available for future
epoll_wait() calls. The last question will trigger a change in my code,
from list_add() to list_add_tail(). Since I don't want to stress Linus
with 24590 patches, I'll wait for 2.5.47 to merge the new code ...



- Davide



      reply	other threads:[~2002-11-08 17:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07 22:53 Jay Vosburgh
2002-11-07 23:24 ` Davide Libenzi
2002-11-08 15:49   ` Mark Hamblin
2002-11-08 17:43     ` Davide Libenzi [this message]

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.44.0211080938081.1768-100000@blue1.dev.mcafeelabs.com \
    --to=davidel@xmailserver.org \
    --cc=MarkHamblin@cox.net \
    --cc=linux-kernel@vger.kernel.org \
    /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®