From: Eugene Surovegin <ebs@ebshome.net>
To: Jacky Lam <jackylam@astri.org>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Small UDP packet performance
Date: Sun, 18 Jan 2004 21:47:51 -0800 [thread overview]
Message-ID: <20040119054751.GB26841@gate.ebshome.net> (raw)
In-Reply-To: <20040119052806.GA26841@gate.ebshome.net>
On Sun, Jan 18, 2004 at 09:28:06PM -0800, Eugene Surovegin wrote:
> Let's say you box is fast enough to send 10K packets per second. As
> you see it's more than enough to saturate 100Mb Ethernet with big
> packets (UDP payload > ~1120 bytes).
>
> But with 200-sized UDP payload you can only fill ~2.7% of 100Mb link.
>
grr, it's 21% of 100Mb link (16% effective (without overhead)).
Eugene.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-19 5:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 3:44 Small UDP packet performance Jacky Lam
2004-01-19 5:28 ` Eugene Surovegin
2004-01-19 5:47 ` Eugene Surovegin [this message]
2004-01-20 0:48 ` Jacky Lam
2004-01-20 1:02 ` Eugene Surovegin
2004-01-20 23:23 ` Andrew May
2004-01-21 1:16 ` Eugene Surovegin
2004-01-21 2:05 ` Andrew May
2004-01-21 3:38 ` Eugene Surovegin
2004-01-22 9:26 ` Jacky Lam
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=20040119054751.GB26841@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=jackylam@astri.org \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).