All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Vehent <julien@linuxwall.info>
To: Netdev <netdev@vger.kernel.org>
Cc: Roel van Meer <rolek@bokxing.nl>, <ahu@ds9a.nl>
Subject: Re: TBF parameters: overhead and linklayer  ?
Date: Tue, 16 Mar 2010 11:21:34 +0100	[thread overview]
Message-ID: <398abc5c97bf8b552252ad85cda742cf@localhost> (raw)
In-Reply-To: <4b0881d1e12a25816f9efac65c4c54ec@localhost>

Gotcha !

in iproute2-2.6.33/tc/tc_util.c

442 int get_linklayer(unsigned int *val, const char *arg)
443 {
444         int res;
445  
446         if (matches(arg, "ethernet") == 0)
447                 res = LINKLAYER_ETHERNET;
448         else if (matches(arg, "atm") == 0)
449                 res = LINKLAYER_ATM;
450         else if (matches(arg, "adsl") == 0)
451                 res = LINKLAYER_ATM;
452         else 
453                 return -1; /* Indicate error */ 
454  
455         *val = res;
456         return 0;
457 }

Now, if I try this, it works:

ses0gnoc:~# tc qdisc add dev eth0 root tbf rate 1mbit burst 10000 latency
10ms linklayer atm

ses0gnoc:~# tc -s qdisc show dev eth0
qdisc tbf 8004: root rate 1000Kbit burst 10000b lat 10.0ms
 Sent 754 bytes 5 pkt (dropped 0, overlimits 0 requeues 0)
 rate 0bit 0pps backlog 0b 0p requeues 0


No ongoing taskforce to rewrite those manpages ? TC is a great tool, but
documentation severely suck...



On Tue, 16 Mar 2010 11:03:28 +0100, Julien Vehent <julien@linuxwall.info>
wrote:
> Thanks Roel,
> 
> I then found this wwebsite from your link http://www.adsl-optimizer.dk
> 
> I'm trying to find more information on how to use this... documentation
is
> really not easily accessible.
> 
> (currently reading latest iproute2 source code available)
> 
> On Tue, 16 Mar 2010 10:06:49 +0100, Roel van Meer <rolek@bokxing.nl>
> wrote:
>> Julien Vehent writes:
>> 
>>> TC_TBF man page seem outdated (even in latest version of iproute2) and
>>> doesn't explain what those two parameters do:
>>> 
>>> # tc qdisc add tbf help
>>> Usage: ... tbf limit BYTES burst BYTES[/BYTES] rate KBPS [ mtu
>>> BYTES[/BYTES] ]
>>>         [ peakrate KBPS ] [ latency TIME ] [ overhead BYTES ] [
> linklayer
>>> TYPE ]
>>> 
>>> 
>>>  - overhead ?
>>>  - linklayer ?
>>> 
>>> Or did I miss something ?
>> 
>> No, you're right. You might want to have a look at this page:
>> http://ace-host.stuart.id.au/russell/files/tc/tc-atm/
>> 
>> Regards,
>> 
>> roel
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-03-16 10:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 16:42 TBF parameters: overhead and linklayer ? Julien Vehent
     [not found] ` <cone.1268730409.349704.27722.1001@bork.lsof.org>
2010-03-16 10:03   ` TBF parameters: overhead and linklayer [UTF-8]? Julien Vehent
2010-03-16 10:21     ` Julien Vehent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-03-16  6:47 TBF parameters: overhead and linklayer ? Julien Vehent

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=398abc5c97bf8b552252ad85cda742cf@localhost \
    --to=julien@linuxwall.info \
    --cc=ahu@ds9a.nl \
    --cc=netdev@vger.kernel.org \
    --cc=rolek@bokxing.nl \
    /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.