<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dear de-bloaters of buffers,<div class="">Esteemed experts of low delay and pacing!</div><div class=""><br class=""></div><div class="">I have no longer been satisfied with high-level descriptions of how pacing works in Linux, and how it interacts with TSQ (I’ve seen some, in various papers, over the years) - but I wanted to REALLY understand it. So, I have dug through the code.</div><div class=""><br class=""></div><div class="">I documented this experience here:</div><div class=""><a href="https://docs.google.com/document/d/1-uXnPDcVBKmg5krkG5wYBgaA2yLSFK_kZa7xGDWc7XU/edit?usp=sharing" class="">https://docs.google.com/document/d/1-uXnPDcVBKmg5krkG5wYBgaA2yLSFK_kZa7xGDWc7XU/edit?usp=sharing</a></div><div class="">but it has some holes and may have mistakes.</div><div class=""><br class=""></div><div class="">Actually, my main problem is that I don’t really know what goes on when I configure a larger IW… things seem to get quite “off” there. Why? Anyone up for solving that riddle? ;-)</div><div class="">(see the tests I documented towards the end of the document)</div><div class=""><br class=""></div><div class="">Generally, if someone who has their hands on files such as tcp_output.c all the time could take a look, and perhaps “fill” my holes, or improve anything that might be wrong, that would be fantastic! I think that anyone should be allowed to comment and make suggestions in this doc.</div><div class=""><br class=""></div><div class="">MANY thanks to whoever finds the time to take a look !</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Michael</div><div class=""><br class=""></div></body></html>