From: "Denys" <nuclearcat@nuclearcat.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] hfsc and bps
Date: Sat, 15 Dec 2007 17:32:08 +0000 [thread overview]
Message-ID: <20071215173208.M4463@nuclearcat.com> (raw)
In-Reply-To: <476380B2.8040101@tuxstef.org>
Already someone answered me before about that... good idea to check first
archive :-)
tip:
tc class add dev ${DEV} parent 1:922 classid 1:925 est 1sec 8sec hfsc sc
dmax 1ms rate 1000kbit ul rate ${ROOTRATE}kbit
est 1sec 8sec
On Sat, 15 Dec 2007 08:22:26 +0100, Stefan Breitegger wrote
> Hi!
>
> Do you know somthing about hfsc and bps?
>
> There's no output for speed only for packets. Doesn't hfsc support
> such a field?
>
> tc -s class show dev eth0
> class hfsc 1: root
> Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
> rate 0bit 0pps backlog 0b 0p requeues 0
> period 0 level 2
>
> class hfsc 1:11 parent 1:1 sc m1 0bit d 18.0ms m2 1000Kbit ul m1
> 0bit d 0us m2 100000Kbit Sent 0 bytes 0 pkt (dropped 0, overlimits 0
> requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 period 0 level 0
>
> class hfsc 1:1 parent 1: sc m1 0bit d 0us m2 100000Kbit ul m1 0bit d
> 0us m2 100000Kbit Sent 0 bytes 0 pkt (dropped 0, overlimits 0
> requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0 period 294075
> work 614619581 bytes level 1
>
> class hfsc 1:10 parent 1:1 sc m1 0bit d 52.9ms m2 99000Kbit ul m1
> 0bit d 0us m2 100000Kbit Sent 614619581 bytes 429677 pkt (dropped 0,
> overlimits 0 requeues 0) rate 0bit 0pps backlog 0b 0p requeues 0
> period 294075 work 614619581 bytes rtwork 614464173 bytes level 0
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-12-15 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 7:22 [LARTC] hfsc and bps Stefan Breitegger
2007-12-15 17:32 ` Denys [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=20071215173208.M4463@nuclearcat.com \
--to=nuclearcat@nuclearcat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox