From: Marc MERLIN <marc@merlins.org>
To: Michael Richardson <mcr@sandelman.ca>
Cc: cerowrt-users@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Cerowrt-users] QOS settings vs speedboost and random bandwidth
Date: Mon, 26 Nov 2012 11:23:17 -0800 [thread overview]
Message-ID: <20121126192317.GE4860@merlins.org> (raw)
In-Reply-To: <9615.1353953507@obiwan.sandelman.ca>
On Mon, Nov 26, 2012 at 01:11:47PM -0500, Michael Richardson wrote:
> dpreed> I'd be happy to think about defining the pieces, but I
> dpreed> really don't have time to code it, given all the other stuff
> dpreed> I've done. I wonder if by putting it in these modules, one
> dpreed> can use existing kernel APIs.
>
> How precise timing do you think we need?
>
> As I understand what you are saying, by periodically sending a few ICMP
> messages (does it help if they are back to back?) and looking when they
> are returned, one can calculate the uplink bandwidth?
By the way, that was kind of what I had in mind.
Capping bandwidth on the router works great for DSL where line bandwidth is
known, but can't really be done right on a cable modem with effectively
variable bandwidth.
I kind of envisionned something where I'd enter the min and max bandwidth
expected, and just like an analog modem, the router would try higher speeds
first, look at how the latency is doing (vs line noise for a modem) and if
it's too high, tone it down.
Then, just like a modem, it could have some algorithm to try ramping back up
from time to time and see what happens (I see this over periods of minutes,
or even hours, not seconds). It wouldn't adapt super quickly, but at the
same time it would also do better than me changing the numbers in the web
interface every so often :)
"How the latency is doing" could indeed be done by sending a traceroute
like packet (TCP or UDP, whatever works) and an ICMP packet to the next hop
up that will reply. All 3 could be done maybe once a minute?
Now I'm not too sure how well that would work for seeing congestion on
uplink vs downlink, but if we know the data that is being shoved in each
direction and it's clearly asymetrical, it ought to be able to make a
reasonable guess that's correct most of the time, no?
Note, I'm not a TCP/IP congestion expert, sorry if what I just wrote isn't
possible for some reason that isn't obvious to me :)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2012-11-26 19:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121125232034.GF24680@merlins.org>
2012-11-26 8:32 ` Dave Taht
2012-11-26 14:22 ` Michael Richardson
2012-11-26 15:04 ` dpreed
2012-11-26 15:38 ` Michael Richardson
2012-11-26 16:37 ` dpreed
2012-11-26 18:11 ` Michael Richardson
2012-11-26 19:23 ` Marc MERLIN [this message]
2012-11-26 19:58 ` dpreed
2012-11-26 21:27 ` Michael Richardson
2012-11-26 22:26 ` dpreed
2012-11-26 15:35 ` Jim Gettys
2012-11-26 18:13 ` Michael Richardson
2012-11-26 18:28 ` Jim Gettys
2012-11-26 21:29 ` Michael Richardson
2012-11-26 15:27 ` Jim Gettys
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121126192317.GE4860@merlins.org \
--to=marc@merlins.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=cerowrt-users@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
/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