From: Bryan Whitehead <driver@jpl.nasa.gov>
To: Svein Ove Aas <svein.ove@aas.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCP send behaviour leads to cable modem woes
Date: Fri, 27 Jun 2003 13:09:28 -0700 [thread overview]
Message-ID: <3EFCA478.7010404@jpl.nasa.gov> (raw)
In-Reply-To: <200306272020.57502.svein.ove@aas.no>
Take a look at the wondershaper script.
It's helped my DSL get good rates from home both up and down...
http://lartc.org/wondershaper/
Svein Ove Aas wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> My internet connection is via a cable modem, and thereon from Telenor. (A
> Norwegian ISP.)
>
> In general, when I download something I can get up to 1400-1500 Kb/s, which is
> pretty good for a 1024/256 account. (They don't appear to oversubscribe their
> lines (yahoo!), but mine is also uncapped when there is spare capacity. Think
> traffic-control.)
>
> So far, so good.
>
> My account includes 4 IP addresses, and when I actually have four computers
> directly connected I can easily get 7-8Kb/s upload from each of them.
> Oddly, when one of them is acting as a firewall/bridge for the others or I'm
> just uploading from one, I get 7-8Kb/s for *all* of them. (Or the one.)
>
> This is, dare I say, *not* expected behaviour.
> I've been in contact with telenor about it, and have garnered the following
> information.
>
> (A) Although the line appear to be straight Ethernet attached to a
> packet-filtering switch (just ARP-filtering, actually), it's *actually* an
> ATM-based line. This should come as no surprise.
>
> (B) Whatever they have allocating the ATM cells for transfer is doing it in
> bursts of about 16KB. Or possibly 32KB. Well, the tech I talked to was pretty
> sure it was a power of two, at least.
>
> (C) This means that while I get 8 bursts (or more) of 16KB per second on
> download (empirically confirmed, but the cable modem will tend to space it
> out when the line is at capacity), giving me a latency of 128-256 ms and so
> on and so forth (which I have), I get only *two* bursts per second to upload
> things. I think. You may want to apply a multiplier somewhere.
>
> And, finally, (D):
>
> This thoroughly screws up TCP/IP for uploading purposes. It *completely*
> breaks Realtek cards, screws up uploading speeds in Linux and Windows XP (I
> assume they think there is a lot of intermittent packet loss because of the
> delay), and has no apparent effect on Windows 9x/2000.
>
> The cable modem in question is manufactured by Coresma and is marked NeMo.
> It's also supposed to have a pretty large send buffer, so if I could just
> force Linux to send at some user-defined speed without being so paranoid
> about overloading the line, I could get a lot more use out of it.
>
> For the curious, if I do just that with UDP, I can indeed send at up to 30KB/s
> without losing packets. They *do* come in bursts, though.
>
>
> Please, save me before I lose my mind!
>
> - - Svein Ove Aas
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (GNU/Linux)
>
> iD8DBQE+/IsG9OlFkai3rMARAmZ4AKCeGIXGhREfh0kcA4Dr8FJs9fNuFgCg1sTb
> 1bk3+ipUs9tS35oZidxcY4I=
> =Zz5P
> -----END PGP SIGNATURE-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Bryan Whitehead
SysAdmin - JPL - Interferometry and Large Optical Systems
Phone: 818 354 2903
driver@jpl.nasa.gov
next prev parent reply other threads:[~2003-06-27 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-27 18:20 TCP send behaviour leads to cable modem woes 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
2003-06-28 15:22 ` Mika Liljeberg
2003-06-28 17:06 ` Svein Ove Aas
2003-06-27 20:09 ` Bryan Whitehead [this message]
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=3EFCA478.7010404@jpl.nasa.gov \
--to=driver@jpl.nasa.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=svein.ove@aas.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.