From: Jason Boxman <jasonb@edseek.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Sharing/splitting bandwidth on a link while bandwidth of the link is variable (or unknow
Date: Wed, 05 Jan 2005 18:19:31 +0000 [thread overview]
Message-ID: <200501051319.31386.jasonb@edseek.com> (raw)
In-Reply-To: <20050105090941.73415.qmail@web51608.mail.yahoo.com>
On Wednesday 05 January 2005 11:59, Jonathan Day wrote:
<snip>
> On the other hand, if it's an exact split over a
> fairly long timeslice, you use a class-based queueing
> system and measure what's been sent out of each queue.
> You then predict what the net bandwidth is over the
> whole timeslice, by looking at what gets sent and what
> gets dropped. Each time you adjust the prediction, you
> adjust the hard limits for the queues to allow out
> whatever is left of that class' net bandwidth.
I wish there was something like that available for PPP over ATM links. My
ADSL connection varies between 160Kbps and 224Kbps depending on how many ATM
cells are wasted by mostly null cells. I'm stuck with a rate of 160Kbps
since that's the lowest stable rate I could find that works under the worst
case scenario of many, small Ethernet packets. Sadly I miss out when my
connection is not in that worst state.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2005-01-05 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 9:09 [LARTC] Sharing/splitting bandwidth on a link while bandwidth of the link is variable (or unknown) ? ngo giang
2005-01-05 12:07 ` [LARTC] Sharing/splitting bandwidth on a link while bandwidth Rene Gallati
2005-01-05 16:59 ` [LARTC] Sharing/splitting bandwidth on a link while bandwidth of the link is variable (or unknow Jonathan Day
2005-01-05 18:19 ` Jason Boxman [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=200501051319.31386.jasonb@edseek.com \
--to=jasonb@edseek.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.