From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Making tcp start transfers slow
Date: Mon, 19 Apr 2004 21:08:02 +0000 [thread overview]
Message-ID: <40843FB2.80503@dsl.pipex.com> (raw)
In-Reply-To: <20040415122135.9743.LARTC@schmakk.dk>
Roy wrote:
> I just had one idea, about this.
>
> what if make iptables module which will make something like enlarged copy
> of syn packet and send it back to the sender?
> (another option would be to kill 1 or 2 ack packets for one syn packet this
> whould force server to reduce speed)
>
>
> that way htb could count upcoming packet and prepare by reducing other
> connetions speed?
> of course that synthetic packet will have higest possible priority since it
> supposed to be appear in future so cant be shaped anyway
>
I don't really get this :-)
>
> I will try to add this functionality to my imq module next week probably.
> ------------------------
> connbytes solution is not good for this, it slows down small picture loading
> in web pages very much, and big downloads get even more "unused" bandwitch.
> so effect is not good. expecialy that looks bad on network, when pages
> become incredibly slow, but big downloads fast.
Depends on lots of things I suppose - the way I have it set new
connections get 256kbit - not that bad for browsing. ISTR seeing one of
your scripts that did similar, IIRC using sfq with low rates. I don't
quite do it like that - for a start sfq 128 queue length is too much and
if you use it on ingress sfq will hash the ~4 simoultaneous connections
your browser makes into one slot. I guess yours simulated a drop with
the reordering when they swapped queues rather than really dropping with
a short queue to get out of slowstart.
SFQ causes instability every time it rehashes on ingress because of this
- there is a todo in the code somewhere. I like to set perturb high.
This ingress shaping with stuff made for egress is a bit tricky - but it
can be tweaked a bit.
Andy.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-04-19 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 10:26 [LARTC] Making tcp start transfers slow Patrick Petersen
2004-04-16 0:55 ` Roy
2004-04-17 23:13 ` Andy Furniss
2004-04-18 0:28 ` Roy
2004-04-19 21:08 ` Andy Furniss [this message]
2004-04-20 1:16 ` Roy
2004-04-22 0:28 ` Patrick Petersen
2004-04-23 23:11 ` Andy Furniss
2004-04-24 11:28 ` Patrick Petersen
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=40843FB2.80503@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.