From: Svein Ove Aas <svein.ove@aas.no>
To: Mika Liljeberg <mika.liljeberg@welho.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCP send behaviour leads to cable modem woes
Date: Sat, 28 Jun 2003 16:04:51 +0200 [thread overview]
Message-ID: <200306281604.52876.svein.ove@aas.no> (raw)
In-Reply-To: <1056743877.681.5.camel@hades>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
fredag 27. juni 2003, 21:57, skrev Mika Liljeberg:
> On Fri, 2003-06-27 at 22:45, Svein Ove Aas wrote:
> > Incidentally, while googling I heard someone saying that only works if
> > it's enabled on both ends? Of course, that might be if upload/download
> > are 'both' affected, in which case it wouldn't apply to me.
>
> It's a sender side only algorithm, so enabling it at your end should be
> enough to help the uploads. For downloads it needs to be on at the other
> end, of course.
Well, it doesn't appear to have any effect.
(What is it *supposed* to do? Something about spurious retransmission
timeouts, was it?)
I'm going to research this a bit more on my own, if none of you have any
further ideas. If I find a solution it should probably be in a HOWTO
somewhere, so I'll get back to you if/when that happens.
- - Svein Ove Aas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+/aCD9OlFkai3rMARAtzFAKCyfXKjWF9yA6wuQZiJvo11RsIs9gCcCBW/
Si1UTkOPaDEtXz5Pq+U64NM=
=kjUX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-28 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 18:20 Svein Ove Aas
2003-06-27 19:02 ` Mika Liljeberg
2003-06-27 19:45 ` Svein Ove Aas
2003-06-27 19:57 ` Mika Liljeberg
2003-06-28 14:04 ` Svein Ove Aas [this message]
2003-06-28 15:22 ` Mika Liljeberg
2003-06-28 17:06 ` Svein Ove Aas
2003-06-27 20:09 ` Bryan Whitehead
2003-06-27 20:24 ` Svein Ove Aas
2003-06-27 20:43 ` Andre Tomt
2003-06-27 22:43 ` Svein Ove Aas
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=200306281604.52876.svein.ove@aas.no \
--to=svein.ove@aas.no \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.liljeberg@welho.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®