From: David Mosberger <davidm@napali.hpl.hp.com>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: davidm@hpl.hp.com, "David S. Miller" <davem@redhat.com>,
kuznet@ms2.inr.ac.ru, jmorris@intercode.com.au,
gandalf@wlug.westbo.se, linux-kernel@vger.kernel.org,
linux-ia64@linuxia64.org, netdev@oss.sgi.com, akpm@digeo.com
Subject: Re: fix TCP roundtrip time update code
Date: Tue, 3 Jun 2003 22:34:30 -0700 [thread overview]
Message-ID: <16093.34022.445246.52398@napali.hpl.hp.com> (raw)
In-Reply-To: <3EDD7832.7010804@us.ibm.com>
>>>>> On Tue, 03 Jun 2003 21:40:18 -0700, Nivedita Singhvi <niv@us.ibm.com> said:
Nivedita> David Mosberger wrote:
DaveM> So if your old SpecWEB99 lab tended more to trigger timeout
DaveM> based retransmits on LAN, and your new test network does not,
DaveM> then your new test network will tend to not reproduce the bug
DaveM> regardless of whether the bug is present in the kernel or not
DaveM> :-)
>> Is this where I get to plug httperf? It triggered the bug
>> reliably in less than 10 secs. ;-)
Nivedita> Tarnation!! Ran httperf! Didnt hit it! :(. What were your
Nivedita> settings?
I used:
$ httperf --rate 1000 --num-conns 1000000 --verbose --hog --server HOST \
--uri pathto30KBfile
on 3 clients (for a total of 3000 conns/sec). You can't go higher
than 1000 conn/sec per client (IP address) because otherwise you run
out of port space (due to TIME_WAIT).
This load worked well for a machine with a single GigE card. All
network tunables were on the default setting (in particular, the tx
queue len was 300, which is were the losses came from).
With this load, I saw bad RTT values in the route cache within a
couple of seconds after starting the third httperf generator. It then
took a bit longer (on the order of 1-2 minutes) until the first
TCPAbortFailed errors started to pop up.
--david
next prev parent reply other threads:[~2003-06-04 5:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 15:52 David Mosberger
2003-06-03 17:41 ` Martin Josefsson
2003-06-03 18:45 ` David Mosberger
2003-06-04 0:24 ` James Morris
2003-06-04 0:43 ` kuznet
2003-06-04 2:01 ` Nivedita Singhvi
2003-06-04 3:23 ` David S. Miller
2003-06-04 4:35 ` David Mosberger
2003-06-04 4:40 ` Nivedita Singhvi
2003-06-04 5:34 ` David Mosberger [this message]
2003-06-04 5:52 ` David S. Miller
2003-06-04 6:12 ` David Mosberger
2003-06-04 6:04 ` Nivedita Singhvi
2003-06-04 6:19 ` David Mosberger
2003-06-04 7:51 ` David S. Miller
2003-06-04 7:21 ` test mail panchi
2003-06-04 4:47 ` fix TCP roundtrip time update code David S. Miller
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=16093.34022.445246.52398@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=gandalf@wlug.westbo.se \
--cc=jmorris@intercode.com.au \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
/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
all inboxes | Powered by JetHome®