<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 17, 2017, at 11:55 PM,<a href="mailto:dave.taht@gmail.com" class="">dave.taht@gmail.com</a> wrote:</div></blockquote><blockquote type="cite" class=""><br class=""><div class=""><div class="">Slotting is a crude approximation of the behaviors of shared media such<br class="">as cable, wifi, and LTE, which gather up a bunch of packets within a<br class="">varying delay window and deliver them, relative to that, nearly all at<br class="">once.<br class=""></div></div></blockquote><div><br class=""></div><div>Nice…</div><div><br class=""></div><div>One of the things I also notice in my LAN tests is latencies for different flows staying at more or less fixed (and different) positions relative to the mean in flent results. Those positions, and the mean, can change with each test run. Do you think this could result from the hashing to different hardware queues (four in my case) changing between test runs? And is it worth trying to simulate this effect, or not really?</div><div><br class=""></div><div>Just for info, in my case (Intel i210) the hashing is documented starting on page 254 of the specs: <a href="https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/i210-ethernet-controller-datasheet.pdf" class="">https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/i210-ethernet-controller-datasheet.pdf</a> (7.1.2.10.1 RSS Hash Function). For TCP/UDP it uses source and destination addresses and ports. I suppose this could be smoothed over in testing by using a spread of ports for the latency test.</div></div></body></html>