From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] CBQ virtual clock
Date: Sat, 15 Dec 2001 03:55:55 +0000 [thread overview]
Message-ID: <marc-lartc-100838859528314@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100837130701320@msgid-missing>
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/
prev parent reply other threads:[~2001-12-15 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-14 23:07 [LARTC] CBQ virtual clock Michael T. Babcock
2001-12-14 23:49 ` bert hubert
2001-12-15 3:55 ` Michael T. Babcock [this message]
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=marc-lartc-100838859528314@msgid-missing \
--to=mbabcock@fibrespeed.net \
--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.