From: Darryl Miles <lartc-list@the-morg.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Newbie HTB shaping question
Date: Tue, 09 Dec 2003 19:59:48 +0000 [thread overview]
Message-ID: <marc-lartc-107100053210061@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107097396006285@msgid-missing>
Martin A. Brown wrote:
>Shaping your outgoing traffic, which is mostly very small TCP ACK packets,
>will do little to shape the much larger packets on the "download" side of
>the stream.
>
Speaking of this, I am currently thinking about doing some research into
shaping of fine grained flows in the reverse direction. My personal
itch I'm looking into scratching is using an abundance of spare CPU
cycles and memory to help improve the inbound queue situation where
bandwidth is limited. In real life situations this would be like a
Pentium 266MHz or better class machine is on the end of a connection
ranging from 128kbit to 8mbit connection.
I'm thinking of using the Linux connection tracker, to make predictions
about each connection it is tracking based on recent usage and/or well
known expected patterns for that particluar service (at connection
creation).
This monitoring would then be able calculate some values to weigh in the
RTT (from this point to the dest and back) and anticipated reverse
payload the destination would return after receipt of this response.
With this information available the outbound packets maybe further
processed in times where the inbound link is saturated, by selecting
packets to delay and/or re-order based on this information, maybe even
performing on the fly TCP window clamping or otherwise altering packets
in an acceptable way. I'm not trying to defeat TCP congestion control
I'm trying to use it to predict the inbound congestion expected at a
time in the immediate future, then tweak the packets I can control to
make ther other end alter its behaviour.
So my questions is does anyone know of any starting points I should look
at on this topic ?
Thanks
Darryl
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-12-09 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 11:37 [LARTC] Newbie HTB shaping question rajkumars
2003-12-09 12:51 ` Jan Gerritsen
2003-12-09 15:43 ` Rajkumar S
2003-12-09 16:15 ` Artūras Šlajus
2003-12-09 16:34 ` Rajkumar S
2003-12-09 16:35 ` Martin A. Brown
2003-12-09 17:19 ` Rajkumar S
2003-12-09 19:59 ` Darryl Miles [this message]
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=marc-lartc-107100053210061@msgid-missing \
--to=lartc-list@the-morg.org \
--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.