From: Randolph Carter <angelripper@cable.net.co>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Bandwidth bounding in a Shared Channel (reused bandwidth)
Date: Fri, 10 Oct 2003 19:59:38 +0000 [thread overview]
Message-ID: <marc-lartc-106581630332731@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106579776311091@msgid-missing>
Sure stef, no aproximation methods? some probabilistic/statistical
approach to the problem?
"The two most common things in the universe are hydrogen and
stupidity."
On Fri, 10 Oct 2003, Stef Coene wrote:
> On Friday 10 October 2003 16:54, Randolph Carter wrote:
> > Sometimes (especially with DSL) in my location when you bought a channel
> > say 128Kbps, there are some "peak" times when you can get even 256Kbps,
> > and another times the channel can go down to least than 128Kbps(in that
> > case the queuing discipline in the box would be doin't but nothing, and
> > the queue would fall into the DSL router). When I used TC + HTB the users
> > complain the speed has dramaticly decreased, and somehow they are right,
> > the channel are not using the peaks(call bursts if you want). How can I do
> > the queing discipline be aware of those changes, any idea; any
> > suggestion?
> This is allmot impossible to implement. You can not 'sense' the speed of the
> link on your shaping box in real time. And that's what you need.
>
> Stef
>
> --
> stef.coene@docum.org
> "Using Linux as bandwidth manager"
> http://www.docum.org/
> #lartc @ irc.openprojects.net
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-10-10 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 14:54 [LARTC] Bandwidth bounding in a Shared Channel (reused bandwidth) Randolph Carter
2003-10-10 19:48 ` Stef Coene
2003-10-10 19:59 ` Randolph Carter [this message]
2003-10-10 20:45 ` Stef Coene
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-106581630332731@msgid-missing \
--to=angelripper@cable.net.co \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox