Re: [LARTC] CBQ virtual clock

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Dec 15, 2001 at 12:49:42AM +0100, bert hubert wrote:
> Enqueue a packet to the queue
> Enqueue a packet to the queue
> Enqueue a packet to the queue
> 	Network interface tells us that there is room
> 	dequeue
> 	dequeue
> [...] 
> The above may not make much sense, but perhaps you can make something of it

Whats interesting is on a couple of occasions I have seen a situation 
where a "ping -n {someone over eth1}" where eth1 is a CBQ'd interface 
will cause something like:

64 bytes from 216.168.105.33: icmp_seq=0 ttl=255 time=3.0 s
64 bytes from 216.168.105.33: icmp_seq=1 ttl=255 time=2.0 s
64 bytes from 216.168.105.33: icmp_seq=2 ttl=255 time=1.0 s
64 bytes from 216.168.105.33: icmp_seq=3 ttl=255 time=0.2 ms

... after a 3 second delay.  I wonder if I could reproduce this and
see if its related to some setting in CBQ.
-- 
Michael T. Babcock
CTO, FibreSpeed Ltd.     (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/



[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux