From: "Sébastien CRAMATTE" <s.cramatte@wanadoo.fr>
To: lartc@vger.kernel.org
Subject: [LARTC] Bridge HFSC QOS ... strange TC values ...
Date: Tue, 05 Dec 2006 20:14:04 +0000 [thread overview]
Message-ID: <4575D30C.2030101@wanadoo.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]
Hello,
I’ve setuped HFSC QOS using as this script
http://automatthias.wordpress.com/2006/06/30/hfsc-and-voip/
I've a bridge with eth0 and eth1 inside br0
I haven't use ebtables, just iptables. I neeed to have different
value on upload and download this why I've setuped QOS on 2 interfaces
Is very strange but root (2:) and main parent (2:2 ) queues still
empty with HFSC
I've got another shapper running with HTB and these 2 queues have got a
value ?????
# tc -s -d class show dev eth1
class hfsc 2: root
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
period 24 work 13844803460630839320 bytes rtwork 20444467840 bytes level
3466779352
class hfsc 2:22 parent 2:2 sc m1 0bit d 10.0s m2 1000Kbit ul m1 0bit d
0us m2 30000Kbit
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
period 24 work 13844803460630839320 bytes rtwork 20444467840 bytes level
3466779352
class hfsc 2:23 parent 2:2 sc m1 0bit d 2.0s m2 1000Kbit ul m1 0bit d
0us m2 30000Kbit
Sent 3545998683 bytes 2796571 pkts (dropped 299, overlimits 0)
period 24 work 13844803460630839320 bytes rtwork 20444467840 bytes level
3466779352
class hfsc 2:2 parent 2: sc m1 0bit d 0us m2 30000Kbit ul m1 0bit d 0us
m2 30000Kbit
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
period 24 work 13844803460630839320 bytes rtwork 20444467840 bytes level
3466779352
class hfsc 2:20 parent 2:2 rt m1 30000Kbit d 50.0ms m2 3000Kbit ls m1
30000Kbit d 50.0ms m2 9000Kbit ul m1 0bit d 0us m2 30000Kbit
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
period 24 work 13844803460630839320 bytes rtwork 20444467840 bytes level
3466779352
class hfsc 2:21 parent 2:2 sc m1 30000Kbit d 200.0ms m2 15000Kbit ul m1
0bit d 0us m2 30000bit
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
period 24 work 13844803460630839320 bytes rtwork 20444467840 bytes level
3466779352
class hfsc 2:24 parent 2:2 sc m1 0bit d 20.0s m2 1000Kbit ul m1 0bit d
0us m2 30000Kbit
Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
period 24 work 13844803460630839320 bytes rtwork 20444467840 bytes level
3466779352
I hope that someone could give me an hand. I can send the script I use
regards
[-- Attachment #2: s.cramatte.vcf --]
[-- Type: text/x-vcard, Size: 457 bytes --]
begin:vcard
fn;quoted-printable:S=C3=A9bastien CRAMATTE
n;quoted-printable:CRAMATTE;S=C3=A9bastien
org:ZEN Soluciones;IT technologies, Linux and Web
adr;quoted-printable:Piso 4b;;Calle Alfonso X el Sabio, 29;Las torres de cotillas;Murcia;30565;Espa=C3=B1a
email;internet:scramatte@zensoluciones.com
title:Consultant
tel;work:+34 968 292 965
tel;cell:+34 627 665 283
x-mozilla-html:FALSE
url:http://www.zensoluciones.com
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2006-12-05 20:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4575D30C.2030101@wanadoo.fr \
--to=s.cramatte@wanadoo.fr \
--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.