Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: dpreed@reed.com
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 13:11:47 -0500	[thread overview]
Message-ID: <9615.1353953507@obiwan.sandelman.ca> (raw)
In-Reply-To: <1353947863.437620265@apps.rackspace.com>


>>>>> "dpreed" == dpreed  <dpreed@reed.com> writes:
    dpreed> But I've thought about coding it again for cerowrt.  Where
    dpreed> to modularly slot it in seems to be worth thinking about.
    dpreed> Perhaps in two key pieces: an iptables/xfilter module and a
    dpreed> routing/traffic control module - with some direct
    dpreed> interaction between the two using some appropriate
    dpreed> intermodule bus/link/coordination link. 

So an uplink bitrate value with an easy to reach sysctl that
userspace can toggle?  It would be an enhancement to existing tc/qos code.
 
    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?

Or are you saying that we are measuring the point in uplink usage where
the latency begins to peak?

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

  reply	other threads:[~2012-11-26 18:12 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 [this message]
2012-11-26 19:23             ` Marc MERLIN
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=9615.1353953507@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=cerowrt-users@lists.bufferbloat.net \
    --cc=dpreed@reed.com \
    /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