From: Jeff Garzik <jgarzik@pobox.com>
To: kirk bae <justformoonie@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: So, Poll is not scalable... what to do?
Date: Tue, 11 Nov 2003 22:52:24 -0500 [thread overview]
Message-ID: <3FB1AE78.2050304@pobox.com> (raw)
In-Reply-To: <LAW12-F60bw5TYIo9WF0002bec8@hotmail.com>
kirk bae wrote:
> If poll is not scalable, which method should I use when writing
> multithreaded socket server?
>
> What is the most efficient model to use?
epoll, thread pools, AIO...
next prev parent reply other threads:[~2003-11-12 3:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 23:52 So, Poll is not scalable... what to do? kirk bae
2003-11-12 3:52 ` Jeff Garzik [this message]
2003-11-12 5:32 ` Willy Tarreau
2003-11-12 23:26 ` bill davidsen
2003-11-13 0:32 ` Davide Libenzi
2003-11-13 0:54 ` Nick Piggin
2003-11-13 12:02 ` Bill Davidsen
2003-11-12 23:23 ` bill davidsen
2003-11-13 1:06 ` Bernd Eckenfels
2003-11-13 7:52 ` David Schwartz
-- strict thread matches above, loose matches on Subject: below --
2003-11-13 18:25 Dan Kegel
2003-11-13 23:10 kirk bae
2003-11-14 0:52 ` Mark Mielke
2003-11-14 0:27 Dan Kegel
2003-11-14 18:57 Frederic Rossi
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=3FB1AE78.2050304@pobox.com \
--to=jgarzik@pobox.com \
--cc=justformoonie@hotmail.com \
--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