netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Heffner <jheffner@psc.edu>
To: lists@limebrokerage.com
Cc: "David S. Miller" <davem@davemloft.net>,
	linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: Possible BUG in IPv4 TCP window handling, all recent 2.4.x/2.6.x kernels
Date: Fri, 2 Sep 2005 10:10:18 -0400	[thread overview]
Message-ID: <6064b8272aa4562242eb60eb75c7cdae@psc.edu> (raw)
In-Reply-To: <Pine.LNX.4.61.0509020948350.6083@guppy.limebrokerage.com>

On Sep 2, 2005, at 10:05 AM, lists@limebrokerage.com wrote:

> This particular Win2k sender sends _only_ real-time data, it's not 
> capable of rewinding. So it's always sending small packets, from start 
> to finish, yet the problem still occurs.
>
> Note that even real-time data can end up generating a stream of 
> full-size packets occassionally. It's just very unlikely they would 
> occur at the start of the flow, as market data is very thin in the 
> pre-market open hours.

The rcv_ssthresh growth can actually take place anywhere in the flow, 
not just at the beginning.



>> But, that window clamping should fix the problem, as we recalculate
>> the window to advertise.
>
> Patches for testing are very much welcome...

Have you tried increasing the size of the receive buffer yet?

   -John


  reply	other threads:[~2005-09-02 14:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.61.0509011713240.6083@guppy.limebrokerage.com>
     [not found] ` <20050901.154300.118239765.davem@davemloft.net>
2005-09-01 22:53   ` Possible BUG in IPv4 TCP window handling, all recent 2.4.x/2.6.x kernels Ion Badulescu
2005-09-01 23:37     ` Jesper Juhl
2005-09-02  2:51     ` John Heffner
2005-09-02  6:28       ` David S. Miller
2005-09-02 14:05         ` lists
2005-09-02 14:10           ` John Heffner [this message]
2005-09-02 14:33             ` lists
2005-09-02 14:48               ` John Heffner
2005-09-02 15:43                 ` Ion Badulescu
2005-09-02 13:02       ` Guillaume Autran
2005-09-02 13:48         ` Ion Badulescu
2005-09-02 13:52         ` Alexey Kuznetsov
2005-09-02 14:11           ` John Heffner
     [not found]           ` <43185E81.2070300@mrv.com>
     [not found]             ` <20050902154424.GA15060@yakov.inr.ac.ru>
2005-09-02 16:18               ` Guillaume Autran
     [not found]               ` <431877EE.6010101@mrv.com>
2005-09-02 17:32                 ` Alexey Kuznetsov
2005-09-02 18:56                   ` Guillaume Autran
2005-09-02 21:08                     ` Alexey Kuznetsov
2005-09-02 13:48       ` Alexey Kuznetsov
2005-09-02 14:16         ` John Heffner
2005-09-02 15:11           ` Alexey Kuznetsov
2005-09-02 18:36     ` Alexey Kuznetsov
2005-09-02 20:57       ` Ion Badulescu
2005-09-02 21:18         ` Alexey Kuznetsov
2005-09-02 23:09           ` Ion Badulescu
2005-09-28 16:31       ` Ion Badulescu
2005-09-29 15:17         ` Alexey Kuznetsov
2005-09-29 15:34           ` Guillaume Autran
2005-09-29 16:04           ` John Heffner
2005-09-29 18:16             ` David S. Miller
2005-09-30  0:29           ` 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=6064b8272aa4562242eb60eb75c7cdae@psc.edu \
    --to=jheffner@psc.edu \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=lists@limebrokerage.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).