From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Denys" Date: Sat, 15 Dec 2007 17:32:08 +0000 Subject: Re: [LARTC] hfsc and bps Message-Id: <20071215173208.M4463@nuclearcat.com> List-Id: References: <476380B2.8040101@tuxstef.org> In-Reply-To: <476380B2.8040101@tuxstef.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.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