Netdev List
 help / color / mirror / Atom feed
From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: [2.6.20.21 review 12/35] TCP: Fix TCP handling of SACK in
Date: Sun, 14 Oct 2007 13:38:51 +0300	[thread overview]
Message-ID: <200710141338.51927.a1426z@gawab.com> (raw)

Ilpo Järvinen wrote:
> Willy Tarreau wrote:
> > I agree with this. The impression I got from the description of the two
> > patches I merged was that the problems they fix were quite annoying. But
> > maybe I should take that with a grain of salt.
>
> No, it's not a grain of salt. I would say its utterly broken, out loud.
> But many people are not that much into time-seq graphs (that I'm familiar
> with), they are pleased when it seems to work well enough even though
> from my perspective, it is simply unacceptable in worst cases (not
> speaking of theoretical ones here, have seen very bad performance). Not
> that it always is that bad, depends on phase of the opposite direction
> what happens.
>
> Somebody asked me when those four patches were made about this, I put
> these there back then:
>
> http://www.cs.helsinki.fi/u/ijjarvin/bidir-showcase/
>
> They are generated from my old test archives and thus may have a bit
> differences in TCP variant, which may slightly differ from mainline
> here and there (my point was just to show how it breaks). Typical
> people wouldn't even notice those minor differences compared with the
> bidir brokeness which is very visible in all except in the fixed "ok"
> case. Please judge for yourself whether I overexaggrated or not... :-)

It would probably be helpful, if you could post a specific testcase and a 
combo-patch of your fixes.


Thanks!

--
Al


                 reply	other threads:[~2007-10-14 10:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200710141338.51927.a1426z@gawab.com \
    --to=a1426z@gawab.com \
    --cc=linux-kernel@vger.kernel.org \
    --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