public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <chris@cybernet.co.nz>
To: linux-kernel@vger.rutgers.edu
Subject: Re: Very poor TCP/SACK performance
Date: Thu, 10 Sep 1998 10:33:44 +1200	[thread overview]
Message-ID: <19980910103344.A16713@caffeine.ix.net.nz> (raw)
In-Reply-To: <19980908232117.A859@math.fu-berlin.de>; from Felix von Leitner on Tue, Sep 08, 1998 at 11:21:17PM +0200

On Tue, Sep 08, 1998 at 11:21:17PM +0200, Felix von Leitner wrote:

> Why is Linux using SACK, anyway? Stevens refers to it like "yeah,
> the BSD people implemented it once, but it didn't work so it was
> discarded and is now obsolete".

I think the context of Stevens probably refers to RFC1072, "TCP
Extensions for Long-Delay Paths", section 3.1. This is dated October
1988, some ten years old.

RFC2018 presumably obsoletes this part, and it looks to me like the
more modern SACK description doesn't fit with the earlier one. This
one is October 1996, not so old.

> And, you know, if Stevens says so, I'd be tempted to just accept
> this as God given and be done with it.  What was the reason to add
> SACK support to Linux?  Almost no system under the sun seems to
> support it, anyway. Right?

S. Floyd et al probably know more about SACK than Stevens and have
done recent (5 years or so) research in this area.

http://www-nrg.ee.lbl.gov/floyd/sacks.html has more details and
recent research efforts which tend to indicate SACK is a way cool
thing that will prevent hair loss reduce global warming.



-Chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/faq.html

       reply	other threads:[~1998-09-09 21:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.02.9809062347430.3952-100000@jeffd.i2k.net>
     [not found] ` <19980908232117.A859@math.fu-berlin.de>
1998-09-09 22:33   ` Chris Wedgwood [this message]
     [not found] <Pine.LNX.4.02.9809081543110.334-100000@jeffd.i2k.net>
1998-09-09  1:14 ` Very poor TCP/SACK performance 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=19980910103344.A16713@caffeine.ix.net.nz \
    --to=chris@cybernet.co.nz \
    --cc=linux-kernel@vger.rutgers.edu \
    /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