From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael T. Babcock" Date: Sat, 15 Dec 2001 03:55:55 +0000 Subject: Re: [LARTC] CBQ virtual clock Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org 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%5 time=3.0 s 64 bytes from 216.168.105.33: icmp_seq=1 ttl%5 time=2.0 s 64 bytes from 216.168.105.33: icmp_seq=2 ttl%5 time=1.0 s 64 bytes from 216.168.105.33: icmp_seq=3 ttl%5 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/ _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/