All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: kuznet@ms2.inr.ac.ru
Cc: James Morris <jmorris@intercode.com.au>,
	davidm@hpl.hp.com, gandalf@wlug.westbo.se,
	linux-kernel@vger.kernel.org, linux-ia64@linuxia64.org,
	netdev@oss.sgi.com, davem@redhat.com, akpm@digeo.com
Subject: Re: fix TCP roundtrip time update code
Date: Tue, 03 Jun 2003 19:01:25 -0700	[thread overview]
Message-ID: <3EDD52F5.8090706@us.ibm.com> (raw)
In-Reply-To: <200306040043.EAA24505@dub.inr.ac.ru>

kuznet@ms2.inr.ac.ru wrote:

> No doubts. All the symptoms are explained by this. I hope Andrew
> will confirm that the problem has gone.

Yep, great catch! But, FYI, DaveM and Alexey, we tried
reproducing the stalls we (Dave Hansen, Troy Wilson) had
seen during SpecWeb99 runs and couldn't reproduce them on
2.5.69. (Same config, etc). So its possible our hang/stalls
were some other issue that got silently fixed (or more
likely, possibly the same thing but other changes minimized
us running into the problem).

thanks,
Nivedita


  reply	other threads:[~2003-06-04  1:55 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 [this message]
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
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=3EDD52F5.8090706@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.