<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
On 2015-5-15, at 06:44, Aaron Wood <<a href="mailto:woody77@gmail.com" class="">woody77@gmail.com</a>> wrote:
<div>
<blockquote type="cite" class="">
<div class=""><span style="font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">ICMP
prioritization over TCP?</span><br class="Apple-interchange-newline">
</div>
</blockquote>
</div>
<br class="">
<div class="">Probably.</div>
<div class=""><br class="">
</div>
<div class="">Ping in parallel to TCP is a hacky way to measure latencies; not only because of prioritization, but also because you don't measure TCP send/receive buffer latencies (and they can be large, auto-tuning is not so great.)</div>
<div class=""><br class="">
</div>
<div class="">You really need to embed timestamps in the TCP bytestream and echo them back. See the recent netperf patch I sent.</div>
<div class=""><br class="">
</div>
<div class="">Lars</div>
</body>
</html>