From: Alan Cox <alan@lxorguk.ukuu.org.uk>
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 09:48:35 +0000 [thread overview]
Message-ID: <1136627315.3748.30.camel@localhost.localdomain> (raw)
In-Reply-To: <f69849430601062302if424acey70e98f86e0de36e6@mail.gmail.com>
On Gwe, 2006-01-06 at 23:02 -0800, kernel coder wrote:
> I noticed that user application started recieveing packets after
> Kernel had recieved all the UDP packets.
If your network chip/ram/processor combination is not fast enough to run
user space applications and handle a full speed network packet stream
then you either need to send more slowly, make the kernel network driver
more efficient or add some kind of interrupt/polling code to reduce
system load to avoid this. The NAPI layer in the networking code is
designed to make this possible.
Probably worth discussing further on netdev@oss.sgi.com
Alan
prev parent reply other threads:[~2006-01-07 9:43 UTC|newest]
Thread overview: 5+ 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
2006-01-07 9:24 ` Kevin D. Kissell
2006-01-07 9:24 ` Kevin D. Kissell
2006-01-07 9:48 ` Alan Cox [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=1136627315.3748.30.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox