From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: [LARTC] TBF settings
Date: Fri, 02 Feb 2001 16:47:53 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416952@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416951@msgid-missing>
<PRE>On Fri, Feb 02, 2001 at 08:38:21AM -0800, Jean-Francois Lemieux wrote:
><i> tc qdisc add dev eth0 parent 1:100 tbf buffer\x15000/8 LIMIT0000 MTU\x1500
</I>><i>
</I>><i> parent class is a cbq with rate\x128Kbit
</I>><i>
</I>><i> when I want to add PEAK, I get always RTNETLINK error: Invalid argument. Maybe be I don't understand this parameter. What I know about it, it's that it can control short-term burst traffic, and it's what I need to do.
</I>
If I remember correctly, you can't 'overspecify' the tbf. So either you set
peak, or you set limit/buffer.
But my recollection is very hazy about this.
Regards,
bert
--
PowerDNS Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
</PRE>
next prev parent reply other threads:[~2001-02-02 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-02 16:38 [LARTC] TBF settings Jean-Francois
2001-02-02 16:47 ` bert [this message]
2001-02-02 17:10 ` Jean-Francois
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-98373940416952@msgid-missing \
--to=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