public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luis Garces <Luis.Garces@eurecom.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: want opinions on possible glitch in 2.4 network error reporting
Date: Thu, 07 Feb 2002 10:22:54 +0100	[thread overview]
Message-ID: <3C62476E.5050700@eurecom.fr> (raw)
In-Reply-To: <E16YcOK-0006wT-00@the-village.bc.nu>

Alan Cox wrote:

 >> I ran into a somewhat related issue on a 2.2.16 system, where I
 >> had an app that was calling sendto() on 217000 packets/sec, even
 >> though the wire could only handle about 127000 packets/sec.  I
 >> got no errors at all in sendto, even though over a third of the
 >> packets were not actually being sent.
 >>
 >
 > That is correct UDP behaviour -
 >

Yes, TCP provides a reliable point-to-point path, and UDP doesn't. The 
problem is considering where does this unreliability starts in the UDP 
path. In Alan's opinion (I think) it starts in the very moment data is 
passed to the call to sendto() (i.e, includes the kernel in the 
unreliable UDP path). Perhaps it is a little sad to see the kernel as 
something lossy, but I think it's the nature of UDP.

-- 
Luis
****


  parent reply	other threads:[~2002-02-07  9:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-06 20:31 want opinions on possible glitch in 2.4 network error reporting Chris Friesen
2002-02-06 20:56 ` Richard B. Johnson
2002-02-06 21:45   ` Ben Greear
2002-02-06 22:23   ` Chris Friesen
2002-02-07 13:44     ` Richard B. Johnson
2002-02-07 16:33       ` Gerold Jury
2002-02-07  0:24   ` Alan Cox
2002-02-07  0:26 ` Alan Cox
2002-02-07  1:51   ` Ion Badulescu
2002-02-07  2:08     ` Alan Cox
2002-02-07  2:09       ` Ion Badulescu
2002-02-07  2:34         ` Alan Cox
2002-02-07  2:54           ` Ion Badulescu
2002-02-07 11:11             ` Alan Cox
2002-02-08 16:11               ` Pavel Machek
2002-02-08 21:39                 ` Ion Badulescu
2002-02-07  4:21       ` Ben Greear
2002-02-07  4:38         ` David S. Miller
2002-02-07  4:56           ` Ben Greear
2002-02-07  4:23     ` Ben Greear
2002-02-07  4:37       ` Ion Badulescu
2002-02-07  9:22   ` Luis Garces [this message]
     [not found] <3C6192A5.911D5B4F@nortelnetworks.com.suse.lists.linux.kernel>
2002-02-07  0:06 ` Andi Kleen
2002-02-07 15:59   ` Chris Friesen
2002-02-07 16:01     ` Andi Kleen
     [not found] <E16Ydys-0007D6-00@the-village.bc.nu.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.44.0202062101390.4832-100000@age.cs.columbia.edu.suse.lists.linux.kernel>
2002-02-07  2:47   ` Andi Kleen
2002-02-07  6:25     ` Chris Friesen

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=3C62476E.5050700@eurecom.fr \
    --to=luis.garces@eurecom.fr \
    --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