From: d@taht.net (Dave Täht)
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] detecting bufferbloat at the DC using ntp?
Date: Tue, 08 Feb 2011 17:49:48 -0700 [thread overview]
Message-ID: <87fwry821f.fsf@cruithne.co.teklibre.org> (raw)
I may have had a wacking good idea this morning.
See ongoing thread on comp.protocols.time.ntp at:
http://lists.ntp.org/pipermail/questions/2011-February/028577.html
--
Dave Taht
http://nex-6.taht.net
next reply other threads:[~2011-02-09 0:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 0:49 Dave Täht [this message]
2011-02-09 5:18 ` [Bloat] monitoring " Dave Täht
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fwry821f.fsf@cruithne.co.teklibre.org \
--to=d@taht.net \
--cc=bloat@lists.bufferbloat.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox