From: Ben Greear <greearb@candelatech.com>
To: Eric Lemoine <Eric.Lemoine@ens-lyon.fr>
Cc: kuznet@ms2.inr.ac.ru, Chris Friesen <cfriesen@nortelnetworks.com>,
hadi@cyberus.CA, netdev@oss.sgi.com
Subject: Re: PATCH Re: udp weirdness
Date: Wed, 02 Oct 2002 08:25:37 -0700 [thread overview]
Message-ID: <3D9B0FF1.1070203@candelatech.com> (raw)
In-Reply-To: 20021002111326.GG357@hookipa
Eric Lemoine wrote:
>>>I may have to poke around...if nothing else I'll learn more about the
>>>networking code...
>>
>>It is difficult task, if possible at all.
>>
>>The main obstacle is that we must not block after select() succeeded,
>>otherwise applications will lockup. Taking into account nature of datagram
>>services (and generally of networking services, where routes change et al.)
>>you do not know at time of select(), where the datagram will go.
>>So, blocking can be made only based on a criterium not depending on this.
>>problems with silent losses. People just do not care about this, so
>>they get the thing which they deserve.
>
>
> Alexey,
>
> Would you mind explaining a bit more why apps will lockup if we block
> after select() succeeded. Or anyone?
Actually, I'm more interested to know why we would **need** to block after
select has succeeded. It would seem to me that select is busted in this
case. For the case of a very large UDP packet and a small send buffer,
select gets confused, but at least when the send buffer is > 128k, it should
be right...
>
> Thx.
>
> Eric.
>
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2002-10-02 15:25 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-24 6:50 udp weirdness Eric Lemoine
2002-09-27 12:02 ` Eric Lemoine
2002-09-27 14:53 ` jamal
2002-09-27 15:04 ` Matti Aarnio
2002-09-29 14:47 ` jamal
2002-09-30 8:49 ` Eric Lemoine
2002-09-30 11:09 ` jamal
2002-09-30 12:10 ` jamal
2002-09-30 12:23 ` jamal
2002-10-01 0:22 ` PATCH " jamal
2002-10-01 6:35 ` Eric Lemoine
2002-10-01 9:51 ` jamal
2002-10-01 13:53 ` kuznet
2002-10-01 14:14 ` jamal
2002-10-01 14:26 ` Chris Friesen
2002-10-01 14:40 ` kuznet
2002-10-01 14:52 ` Chris Friesen
2002-10-01 15:31 ` kuznet
2002-10-01 16:16 ` Chris Friesen
2002-10-01 16:41 ` kuznet
2002-10-01 17:17 ` Chris Friesen
2002-10-01 16:42 ` Ben Greear
2002-10-01 16:58 ` Chris Friesen
2002-10-01 17:55 ` jamal
2002-10-01 18:36 ` Chris Friesen
2002-10-01 18:35 ` jamal
2002-10-01 18:54 ` Ben Greear
2002-10-01 19:03 ` Chris Friesen
2002-10-01 18:52 ` Ben Greear
2002-10-02 11:13 ` Eric Lemoine
2002-10-02 14:09 ` Chris Friesen
2002-10-02 15:25 ` Ben Greear [this message]
2002-10-03 15:58 ` Eric Lemoine
2002-10-03 16:29 ` kuznet
2002-09-27 15:19 ` Eric Lemoine
2002-09-27 15:57 ` Eric Lemoine
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=3D9B0FF1.1070203@candelatech.com \
--to=greearb@candelatech.com \
--cc=Eric.Lemoine@ens-lyon.fr \
--cc=cfriesen@nortelnetworks.com \
--cc=hadi@cyberus.CA \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).