From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: incoming packet latency in 2.4.[18-20]
Date: Wed, 15 Oct 2003 11:45:52 -0400 [thread overview]
Message-ID: <3F8D6BB0.7060809@nortelnetworks.com> (raw)
There is an issue with incoming packet latency in the kernels mentioned.
It seems that if you send in a burst of messages, the amount of time it
takes to wake the listening process is dependent on the size of the
message burst. 2.4.18-2.4.20 all show this behaviour, 2.6 doesn't.
Some numbers for a udp message size of 2 bytes:
1 packet, average latency 12 usecs
10 packets, average latency 66 usecs
100 packets, average latency 477 usecs
Is this a known issue? Is there an easy way to fix this, or is it
something inherent in the 2.4 architecture?
Thanks,
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next reply other threads:[~2003-10-15 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 15:45 Chris Friesen [this message]
2003-10-15 16:15 ` incoming packet latency in 2.4.[18-20] Matt H.
2003-10-15 16:16 ` Stephan von Krawczynski
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=3F8D6BB0.7060809@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--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