All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: davidm@hpl.hp.com
Cc: "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, 03 Jun 2003 21:40:18 -0700	[thread overview]
Message-ID: <3EDD7832.7010804@us.ibm.com> (raw)
In-Reply-To: <16093.30507.661714.676184@napali.hpl.hp.com>

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. ;-)

Tarnation!! Ran httperf! Didnt hit it! :(. What were your
settings?

I extracted an old debug patch to implement dropping of
packets - have a sysctl that controls the rate at which I
can drop IP packets, so can also generate any kind of packet
loss..So thought I would bang away with netperf using
sendfile()/TCP_CORK. Thought it was in that code path.
Will be running tests tmrw and the rest of this
week on 2.5.70 +- patch. Will see if I can provoke any
further hangs, stalls, wackiness of any flavor...

thanks,
Nivedita



  reply	other threads:[~2003-06-04  4:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-03 15:52 fix TCP roundtrip time update code 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 [this message]
2003-06-04  5:34                 ` David Mosberger
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=3EDD7832.7010804@us.ibm.com \
    --to=niv@us.ibm.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 \
    /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.