From: Christoph Lameter <cl@linux-foundation.org>
To: Mark Smith <lk-netdev@lk-netdev.nosense.org>
Cc: netdev@vger.kernel.org
Subject: Re: Low latency diagnostic tools
Date: Thu, 6 Aug 2009 10:19:53 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.10.0908061017001.5507@gentwo.org> (raw)
In-Reply-To: <20090806094736.591b7086.lk-netdev@lk-netdev.nosense.org>
On Thu, 6 Aug 2009, Mark Smith wrote:
> This implementation of One Way Active Measurement Protocol might be of
> interest:
>
> http://www.internet2.edu/performance/owamp/
It needs an accurate timesource. So it wont be of general use unless
everyone adopts ptp or so. Latencies today are way below 100 microseconds
which is not doable with the accuracy provided by ntp.
> Some of the performance tuning parts of the README below would also be
> useful in the Net area of the Linux Foundation wiki. Possibly the
> "Testing" section could be changed to "Testing and Measurement"
>
> http://www.linuxfoundation.org/en/Net:Main_Page
Ok. I will look at that.
prev parent reply other threads:[~2009-08-06 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 21:10 Low latency diagnostic tools Christoph Lameter
2009-08-06 0:17 ` Mark Smith
2009-08-06 14:19 ` Christoph Lameter [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=alpine.DEB.1.10.0908061017001.5507@gentwo.org \
--to=cl@linux-foundation.org \
--cc=lk-netdev@lk-netdev.nosense.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox