From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TCP window based shaping
Date: Tue, 15 Mar 2005 15:24:31 +0000 [thread overview]
Message-ID: <4236FE2F.4020908@wildgooses.com> (raw)
In-Reply-To: <42095013.8030600@wildgooses.com>
>In my current implementation at home, I use TC/HTB rules to priortise
>outgoing acks. This definately helps esp when doing huge Linux ISO dl's
>through Bittorrent.
>
>Why delay Acks?? Just because you want to delay/make/simulate the normal
>TCP behaviour of making the window smaller??
>
>
...because "we" don't want bittorrent to go faster....
The goal is to slow things down, not speed them up. Granted though that
prioritising acks is useful up until the client is using the desired
amount of bandwidth, after that we want to slow them down again
Ed W
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-03-15 15:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 23:49 [LARTC] TCP window based shaping Ed Wildgoose
2005-02-08 23:57 ` David Boreham
2005-02-09 1:59 ` Andy Furniss
2005-02-09 11:34 ` marco ghidinelli
2005-02-09 22:38 ` Andy Furniss
2005-02-11 2:57 ` Ed Wildgoose
2005-02-11 11:05 ` marco ghidinelli
2005-02-11 18:18 ` Ed Wildgoose
2005-02-11 23:45 ` Ed Wildgoose
2005-02-12 2:16 ` Andy Furniss
2005-02-12 13:19 ` Andy Furniss
2005-02-13 0:46 ` Ed Wildgoose
2005-02-14 0:27 ` marco ghidinelli
2005-02-14 0:38 ` marco ghidinelli
2005-02-15 22:33 ` Andy Furniss
2005-02-15 22:54 ` Andy Furniss
2005-02-16 14:52 ` Ed Wildgoose
2005-02-17 3:45 ` gypsy
2005-02-17 14:09 ` Ed Wildgoose
2005-03-12 10:10 ` Ow Mun Heng
2005-03-15 15:24 ` Ed Wildgoose [this message]
2005-03-16 7:46 ` Ow Mun Heng
2005-07-09 4:01 ` Don Cohen
2005-07-10 19:55 ` Andy Furniss
2005-07-12 1:50 ` TAKANO Ryousei
2005-07-12 8:46 ` Andy Furniss
2005-07-12 13:44 ` TAKANO Ryousei
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=4236FE2F.4020908@wildgooses.com \
--to=lists@wildgooses.com \
--cc=lartc@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 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.