All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brett Foster <fosterb@uoguelph.ca>
To: kernel coder <lhrkernelcoder@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Almost 80% of UDP packets dropped
Date: Sat, 07 Jan 2006 02:38:11 -0500	[thread overview]
Message-ID: <43BF6FE3.7030600@uoguelph.ca> (raw)
In-Reply-To: <f69849430601062302if424acey70e98f86e0de36e6@mail.gmail.com>

kernel coder wrote:

>hi,
>    I was trying to measure the UDP reception speed on my borad which
>has MIPS 4kc processor with 133 MHZ speed.I was transfering 10mb file
>from intel pentium 4 machine to MIPS board,but the recieved file was
>only 900kB.
>  
>
UDP was not designed with reliability in mind -- it really isn't meant 
for sending a 10 meg file without a packet loss.

>When i further investigated the problem ,i came to know that the user
>application was not getting enough opportunities to get data from
>socket queue which caused almost 80% of packets to be dropped as
>socket queue had no free space.
>  
>
(Among other sources) I'm pretty sure this behaviour was discussed in:
Unix Network Programming, Vol. 1: The Sockets Networking API, Third Edition
(Something like page 257.)

I don't know if there is anything else going on with the kernel but...

Brett

  reply	other threads:[~2006-01-07  7:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07  7:02 Almost 80% of UDP packets dropped kernel coder
2006-01-07  7:38 ` Brett Foster [this message]
2006-01-07  9:24 ` Kevin D. Kissell
2006-01-07  9:24   ` Kevin D. Kissell
2006-01-07  9:48 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2006-01-07  7:03 kernel coder
2006-01-07 15:04 ` Denis Vlasenko
2006-01-07 15:23   ` Tomasz Torcz
2006-01-07 21:19     ` Jan Engelhardt
2006-01-07 22:44       ` Tomasz Torcz
2006-01-09  5:52         ` kernel coder
2006-01-07 22:35   ` Bernd Eckenfels

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=43BF6FE3.7030600@uoguelph.ca \
    --to=fosterb@uoguelph.ca \
    --cc=lhrkernelcoder@gmail.com \
    --cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.