netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Bredesen <cbredesen@redhat.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: Netdev <netdev@vger.kernel.org>, johnwheffner@gmail.com
Subject: Re: Debugging TCP: Treason Uncloaked
Date: Mon, 19 May 2008 12:40:39 -0400	[thread overview]
Message-ID: <4831AD87.1040909@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805121637560.1888@wrl-59.cs.helsinki.fi>

[-- Attachment #1: Type: text/plain, Size: 1500 bytes --]

Ilpo Järvinen wrote:
> ...This report lacks kernel version (no I won't try to figure out what f8 
> or whatever is using on your box, just tell it :-)) (e.g., ...Some 
> 2.6.25-rc had this problem).
> 
> Tcp_window_scaling sysctl has nothing to do with window resizing. ...It 
> just decides if scaling factor can be used or not. It won't guarantee you 
> a constant window!
> 
> What happened while the window was shrunk is hard to know because the log 
> snippet doesn't have the point where the window was reduced.

John - thanks for the explanation - I understand the relationship 
between scaling and resizing now.  If my notes are correct, it happened 
with both these kernels on the client:

2.6.24.3-12.fc8.i686
2.6.24.3-34.fc8.i686

RHEL and CentOS guys are reporting this issue as well so I wonder if 
it's something specific to a RH kernel (not sure how close they are to 
upstream but my understanding is that Fedora kernels are pretty close, 
but this is *clearly* not my area of expertise).

Kernel on the NAS device is 2.6.9 AFAIK but the distro has proprietary 
bits in it so I'm not sure what's been done there.  It's a Netgear 
ReadyNAS appliance.

In any case, I'm attaching an archive of the whole tcpdump session so 
you can have a look.   Please let me know if you need more info.  I 
really *really* appreciate your help on this -- I'm paying the results 
of our findings forward so others won't get tripped up on this issue.

Best,

Chris

[-- Attachment #2: tcp.dump.filtered.tar.gz --]
[-- Type: application/x-gzip, Size: 106507 bytes --]

  reply	other threads:[~2008-05-19 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  2:29 Debugging TCP: Treason Uncloaked Chris Bredesen
2008-05-08 15:01 ` John Heffner
2008-05-13 11:21 ` Ilpo Järvinen
2008-05-19 16:40   ` Chris Bredesen [this message]
2008-05-20 10:17     ` Ilpo Järvinen

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=4831AD87.1040909@redhat.com \
    --to=cbredesen@redhat.com \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=johnwheffner@gmail.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).