search for: 0us

Hi, I''m trying to get a handle on hfsc. Here is my configuration: root@jmnrouter:/jmn# tc class show dev vlan1 class hfsc 1: root class hfsc 1:1 parent 1: ls m1 0bit d 0us m2 225000bit ul m1 0bit d 0us m2 225000bit class hfsc 1:10 parent 1:1 rt m1 191000bit d 25.0ms m2 135000bit ls m1 0bit d 0us m2 135000bit ul m1 0bit d 0us m2 225000bit class hfsc 1:20 parent 1:1 rt m1 22008bit d 25.0ms m2 56008bit ls m1 0bit d 0us m2 56008bit ul m1 0bit d 0us m2 225000bit class hfs...

...3. the upper-limit applies, traffic doesn''t do up more than 4kb/s. The 1:4 is still functional, but 1:2, the default class starts backlogging and dropping as hell: class hfsc 1: root Sent 0 bytes 0 pkts (dropped 0, overlimits 0) period 0 level 2 class hfsc 1:1 parent 1: ls m1 0bit d 0us m2 512000bit ul m1 0bit d 0us m2 512000bit Sent 0 bytes 0 pkts (dropped 0, overlimits 0) <-- This is weird too ^_^ period 2643 work 821712 bytes level 1 class hfsc 1:2 parent 1:1 ls m1 0bit d 0us m2 2000bit ul m1 0bit d 0us m2 400000bit Sent 477205 bytes 3874 pkts (dropped 0, overlimits...

...e this root@ubuntu:/home/shaper# tc -s -d class ls dev eth2 class hfsc 1: root Sent 0 bytes 0 pkts (dropped 0, overlimits 0) period 24 work 13844792199226589188 bytes rtwork 20937281664 bytes level 3461036864 class hfsc 1:11 parent 1:1 sc m1 30720Kbit d 10.0ms m2 30000bit ul m1 0bit d 0us m2 300000bit Sent 332564 bytes 235 pkts (dropped 0, overlimits 0) period 24 work 13844792199226589188 bytes rtwork 20937281664 bytes level 3461036864 class hfsc 1:1 parent 1: sc m1 0bit d 0us m2 10000bit ul m1 0bit d 0us m2 10000Kbit Sent 0 bytes 0 pkts (dropped 0, overlimits 0) period 24...

...0000000: ioctl: create device v0 device ffffffffffffffff [ 4620.356005] nouveau: DRM:00000000:00000080: init running... [ 4620.356006] nouveau 0000:01:00.0: preinit running... [ 4620.356006] nouveau 0000:01:00.0: pci: preinit running... [ 4620.356007] nouveau 0000:01:00.0: pci: preinit completed in 0us [ 4620.356008] nouveau 0000:01:00.0: bios: preinit running... [ 4620.356008] nouveau 0000:01:00.0: bios: preinit completed in 0us [ 4620.356009] nouveau 0000:01:00.0: devinit: preinit running... [ 4620.356024] nouveau 0000:01:00.0: devinit: preinit completed in 14us [ 4620.356024] nouveau 0000:01:0...

...ent 0 bytes 0 pkts (dropped 0, overlimits 0) >qdisc sfq 17: > Sent 1857 bytes 24 pkts (dropped 0, overlimits 0) =>tc -s -d class show dev $MYDEV >class hfsc 1: root > Sent 0 bytes 0 pkts (dropped 0, overlimits 0) > period 0 level 2 > >class hfsc 1:10 parent 1: sc m1 0bit d 0us m2 243208bit ul m1 0bit d 0us m2 243208bit > Sent 0 bytes 0 pkts (dropped 0, overlimits 0) > period 26 work 179610 bytes level 1 > >class hfsc 1:1 parent 1:10 rt m1 0bit d 0us m2 2000bit > Sent 173952 bytes 2232 pkts (dropped 0, overlimits 0) > period 0 work 173952 bytes rtwork 17...

I don''t understand the following: root@jmnrouter:~# tc -s class ls dev vlan1 && tc -s qdisc ls dev vlan1 class hfsc 1: root Sent 0 bytes 0 pkts (dropped 0, overlimits 0) period 0 level 2 class hfsc 1:1 parent 1: sc m1 0bit d 0us m2 220000bit ul m1 0bit d 0us m2 220000bit Sent 0 bytes 0 pkts (dropped 0, overlimits 0) period 31304 work 7533852 bytes level 1 class hfsc 1:10 parent 1:1 sc m1 1024bit d 8.0ms m2 100000bit ul m1 0bit d 0us m2 220000bit Sent 6892869 bytes 33300 pkts (dropped 0, overlimits 0) period 32750 wor...

...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...

Hello, I''ve got somes questions about Bridge and QOS ... I''ve got a serveur with 2 interfaces eth0,eth1 inside br0 bridge ... nothing of special ... If I understand all, normally I should configure TC class and qdisc on each physical or use ebtables to manage packets on output ... right ? I''ve attached my qos_script that hsfc and layer7 module. I use only Iptables

...mpleted in 1us Feb 28 23:07:11 laptop kernel: [ 13.753039] nouveau: DRM:00000000:8000900b: init running... Feb 28 23:07:11 laptop kernel: [ 13.753040] nouveau: DRM:00000000:8000900b: init children... Feb 28 23:07:11 laptop kernel: [ 13.753041] nouveau: DRM:00000000:8000900b: init completed in 0us Feb 28 23:07:11 laptop kernel: [ 13.753046] nouveau: DRM:00000000:0000917d: init running... Feb 28 23:07:11 laptop kernel: [ 13.753072] nouveau: DRM:00000000:0000917d: init children... Feb 28 23:07:11 laptop kernel: [ 13.753073] nouveau: DRM:00000000:0000917d: init completed in 25us Feb 28 23...

...> Feb 28 23:07:11 laptop kernel: [ 13.753039] nouveau: DRM:00000000:8000900b: init running... > Feb 28 23:07:11 laptop kernel: [ 13.753040] nouveau: DRM:00000000:8000900b: init children... > Feb 28 23:07:11 laptop kernel: [ 13.753041] nouveau: DRM:00000000:8000900b: init completed in 0us > Feb 28 23:07:11 laptop kernel: [ 13.753046] nouveau: DRM:00000000:0000917d: init running... > Feb 28 23:07:11 laptop kernel: [ 13.753072] nouveau: DRM:00000000:0000917d: init children... > Feb 28 23:07:11 laptop kernel: [ 13.753073] nouveau: DRM:00000000:0000917d: init completed in...

Hi i have found a problem related with tbf and the latency that the tbf calculates.. I have used the following parameters for burst and limit burst 100Kbit limit 500Kbit lat81.8ms burst 6Kbit limit 6Kbit lat 0us burst 200Kbit limit 100Kbit lat 4294.9s As u can see in the 3rd column the latency for 100Kbit burst and 500Kbit limit is 81.8ms but for 200Kbit and limit 100Kbit is 4294.9s!!! How could be possible??? I want to find a way to caclulate the latency for a packet entering my tbf.. What do u suggest...

...@ubuntu:~$ tc -s -d class ls dev eth2 class hfsc 1: root Sent 0 bytes 0 pkts (dropped 0, overlimits 0) period 3223398930 work 14505631817980074884 bytes rtwork 14544911558267371524 b ytes level 3377421952 class hfsc 1:11 parent 1:1 leaf 11: rt m1 12000bit d 100.0ms m2 200000bit ls m1 0bit d 0us m2 200000bit ul m1 0bit d 0us m2 350000bit Sent 252678 bytes 3405 pkts (dropped 0, overlimits 0) period 3223398930 work 14505631817980074884 bytes rtwork 14544911558267371524 b ytes level 3377421952 thank you raku --------------------------------- All-new Yahoo! Ma...

...fileset pre-allocation to finish 1062: 108.612: Starting 1 rand-read instances 1063: 109.617: Starting 1 rand-thread threads 1062: 112.627: Running... 1062: 213.627: Run took 100 seconds... 1062: 213.628: Per-Operation Breakdown rand-rate 0ops/s 0.0mb/s 0.0ms/op 0us/op-cpu rand-read1 41845ops/s *1307.7mb/s* 0.0ms/op 20us/op-cpu 1062: 213.628: IO Summary: 4226337 ops, 41845.0 ops/s, (41845/0 r/w) 1307.7mb/s, 21us cpu/op, 0.0ms latency 1062: 213.628: Shutting down processes -------------------------------------------------------------...

...${TC} qdisc add dev ${LAN_IFACE} parent 1:60 handle 60: esfq hash dst perturb 10 # tc -s -d class show dev eth1 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 3 class hfsc 1:1 parent 1: ls 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 25105 work 9541169 bytes level 2 ........... class hfsc 1:60 parent 1:3 leaf 60: rt m1 0bit d 500.0ms m2 32008bit ls m1 0bit d 3.0s m2 690000bi...

...e rest. Question 1: I defined the voip qdisc as tc class add dev ppp0 parent 1:1 classid 1:11 \ hfsc sc umax 1500b dmax 30ms rate 500kbit ul rate 900kbit but "tc -s class show dev ppp0" shows class hfsc 1:11 parent 1:1 sc m1 0bit d 6.0ms m2 500000bit \ ul m1 0bit d 0us m2 900000bit Where does the "0bit d 6.0ms" come from, (what does the other stuff exactly mean) and what would be a good setting for voip traffic? This qdisc only affects outgoing traffic. But I also want to control incoming packets and keep the isp''s queue empty. Question...

...ting APIC timer for CPU0... ..... CPU speed is 1129.5684 MHz. ..... Bus speed is 132.8903 MHz. ..... bus_scale = 0x00008814 ACT: Initialising Accurate timers Time init: .... System Time: 11843241ns .... cpu_freq: 00000000:43541940 .... scale: 00000001:C5438A0E .... Wall Clock: 1092158215s 0us Start schedulers PCI: PCI BIOS revision 2.10 entry at 0xfbfee, last bus=1 PCI: Using configuration type 1 PCI: Probing PCI hardware Transparent bridge - PCI device 8086:244e PCI: Using IRQ router PIIX [8086/2440] at 00:1f.0 PCI: Found IRQ 11 for device 01:0c.0 3c59x: Donald Becker and others. www.s...

...ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range AB, TimeoutDis+, LTR+, OBFF Via message DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB Lnk...

CPUIDLE: Avoid remnant LAPIC timer intr while force hpetbroadcast LAPIC will stop during C3, and resume to work after exit from C3. Considering below case: The LAPIC timer was programmed to expire after 1000us, but CPU enter C3 after 100us and exit C3 at 9xxus. 0us: reprogram_timer(1000us) 100us: entry C3, LAPIC timer stop 9xxus: exit C3 due to unexpected event, LAPIC timer continue running 10xxus: reprogram_timer(1000us), fail due to the past expiring time. ......: no timer softirq raised, no chan...

...PU clock speed is 451.0303 MHz. +(XEN) ..... host bus clock speed is 100.2288 MHz. (XEN) ..... bus_scale = 0x000066A2 (XEN) Time init: -(XEN) .... System Time: 12217304ns -(XEN) .... cpu_freq: 00000000:1AE22E48 -(XEN) .... scale: 00000002:3796C7A7 -(XEN) .... Wall Clock: 1114087225s 40000us +(XEN) .... System Time: 80262159ns +(XEN) .... cpu_freq: 00000000:1AE24040 +(XEN) .... scale: 00000002:37954C49 +(XEN) .... Wall Clock: 1114087099s 0us (XEN) PCI: PCI BIOS revision 2.10 entry at 0xf08c0, last bus=1 (XEN) PCI: Using configuration type 1 (XEN) PCI: Probing PCI hardware...

hmm HFSC ? where can i find more informations and examples about the *linux* HFSC ? http://trash.net/~kaber/hfsc/ does not help here -- _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/