From: khandelw@cs.fsu.edu
To: Mike Jagdis <mjagdis@eris-associates.co.uk>
Cc: jyotiraditya@softhome.net, linux-kernel@vger.kernel.org
Subject: Re: Select/Poll
Date: Thu, 3 Jun 2004 11:53:35 -0400 [thread overview]
Message-ID: <1086278015.07e5e9ff7c143@system.cs.fsu.edu> (raw)
In-Reply-To: <20040603151058.GA3169@eris-associates.co.uk>
I meant it in the context of TCP. I thought it was implicit enough, because if
he was using UDP then packet loss is expected. (not necessary that it will
happen)
- Amit Khandelwal
Quoting Mike Jagdis <mjagdis@eris-associates.co.uk>:
> On Wed, Jun 02, 2004 at 11:28:29AM -0400, khandelw@cs.fsu.edu wrote:
> > Hello,
> > Can you give more details - Like which machine which vendor etc.,
> > On a sony vaio pcg frv31 laptop/ redhat 9.0/ after firing some 36,000+
> request
> > my select multiplexed server used to fail. With select I believe you not
> get
> > any packet loss...
>
> Then you'd be wrong. Poll/select tell you when desriptors
> are readable/writable. They do *not* impose any magic queuing
> mechanism that guarantees the buffers won't overflow. If the
> low level protocol is non-flow controlled like UDP you *have*
> to read data faster than it arrives and not write data faster
> than it is being transmitted.
>
> Mike
>
> --
> Mike Jagdis Web: http://www.eris-associates.co.uk
> Eris Associates Limited Tel: +44 7780 608 368
> Reading, England Fax: +44 118 926 6974
>
prev parent reply other threads:[~2004-06-03 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 5:33 Select/Poll jyotiraditya
2004-06-02 5:54 ` Select/Poll David Schwartz
2004-06-02 6:12 ` Select/Poll Ben Greear
2004-06-02 6:38 ` Select/Poll bert hubert
2004-06-02 6:09 ` Select/Poll Ben Greear
2004-06-02 7:05 ` Select/Poll Vadim Lobanov
2004-06-02 14:11 ` Select/Poll Davide Libenzi
2004-06-02 15:28 ` Select/Poll khandelw
2004-06-03 15:10 ` Select/Poll Mike Jagdis
2004-06-03 15:53 ` khandelw [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=1086278015.07e5e9ff7c143@system.cs.fsu.edu \
--to=khandelw@cs.fsu.edu \
--cc=jyotiraditya@softhome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjagdis@eris-associates.co.uk \
/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