From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] leaky bucket on bursty multicast
Date: Wed, 01 Mar 2006 21:03:27 +0000 [thread overview]
Message-ID: <44060C1F.4090006@dsl.pipex.com> (raw)
In-Reply-To: <ac81ed350602150442l2968563cm306cfea79f2c1138@mail.gmail.com>
Oivind wrote:
> Hi all,
> I have an average 2mbit multicast stream that once in a while bursts
> high (up to 20mbit/s) in short periods (about 200ms). Could anyone
> please help me with directions using tc for configuing leaky bucket
> shaping to this stream? I have a 5mbit/s ceiling.
>
> My system is running gentoo linux 2.6.14, and I have compiled in all
> QoS modules.
I suppose it depends what you want to do with the burst ie. propogate it
,smooth it without loss or drop packets to maintain a rate.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-03-01 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 12:42 [LARTC] leaky bucket on bursty multicast Oivind
2006-03-01 21:03 ` Andy Furniss [this message]
2006-03-08 16:05 ` Oivind
2006-04-07 22:03 ` Andy Furniss
2006-05-24 11:18 ` Oivind
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=44060C1F.4090006@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.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.