<div dir="ltr"><div dir="ltr">On Tue, Nov 22, 2022 at 2:43 PM 'Bob McMahon' via BBR Development <<a href="mailto:bbr-dev@googlegroups.com">bbr-dev@googlegroups.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Thanks for sharing this. Curious about how the xTSQ value can be set? Can it be done with sysctl?<br><br><i>We continue our analysis by using the ms-version of TSQ
patch, which enables the tune of the TSQ size allowing each
TCP variant to enqueue more than 1 ms of data at the current
TCP rate. In particular, we allow to enqueue the equivalent
of x ms of data, naming each test xTSQ, with x being an
integer value. <span style="background-color:rgb(255,255,0)"><b>It is important to notice that this patch has been
included in the Linux kernel mainline, and each Wi-Fi driver
can now set the desired xTSQ value</b></span></i><b>.</b></div></div></blockquote><div><br></div><div>I believe they are setting the xTSQ value using the sk_pacing_shift field, which was added here:</div><div> <a href="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a9b76fd0db9f0d426533f96a68a62a58753a51e">https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a9b76fd0db9f0d426533f96a68a62a58753a51e</a></div><div><br></div><div>AFAIK the intent is only for drivers to set that, and there's no sysctl for that, but of course you could add a sysctl for testing if you wanted. :-)</div><div><br></div><div>cheers,</div><div>neal</div><div><br></div><div><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div class="gmail_attr">Another thing that could be interesting is the WiFi aggregation stop reasons, e.g. how many times agg stopped per hitting the max mpdu per ampdu vs the software fifo going empty (i.e. no more packets available to the driver from the TCP stack) per that TXOP.<br><br>Finally, many (most?) APs are forwarding and feeding packets at at the hardware level so not sure that the linux stack matters as much for an AP based analysis, particularly when considering multi user transmissions, i.e. multiple WiFi clients are active and sharing TXOPs.<br><br>Bob</div><div dir="ltr" class="gmail_attr">On Mon, Nov 21, 2022 at 10:04 PM Dave Taht <<a href="mailto:dave.taht@gmail.com" target="_blank">dave.taht@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">This paper came out last month. Good work, really exhaustive look at<br>
two chipsets, multiple congestion controls and the interactions with<br>
TSQ, with<br>
lots and lots of flent.<br>
<br>
<a href="https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=9772053" rel="noreferrer" target="_blank">https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=9772053</a><br>
<br>
as for wifi6... don't make me start talking about wifi6... but some of<br>
these tests look like a good baseline to start comparing the ath11k,<br>
mt79, etc..<br>
<br>
Paper kind of misses the negative impact of AQL in the ath10k (and<br>
most likely also the mt76 and mt79 chips)<br>
<br>
-- <br>
This song goes out to all the folk that thought Stadia would work:<br>
<a href="https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz" rel="noreferrer" target="_blank">https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz</a><br>
Dave Täht CEO, TekLibre, LLC<br>
<br>
-- <br>
You received this message because you are subscribed to the Google Groups "BBR Development" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:bbr-dev%2Bunsubscribe@googlegroups.com" target="_blank">bbr-dev+unsubscribe@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/bbr-dev/CAA93jw6yJU10wh9ajqX4yW2AvnJPStyWAAcV4%2BoQ8wSGsJgKZA%40mail.gmail.com" rel="noreferrer" target="_blank">https://groups.google.com/d/msgid/bbr-dev/CAA93jw6yJU10wh9ajqX4yW2AvnJPStyWAAcV4%2BoQ8wSGsJgKZA%40mail.gmail.com</a>.<br>
</blockquote></div></div>
<br>
<span style="background-color:rgb(255,255,255)"><font size="2">This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.</font></span>
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups "BBR Development" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:bbr-dev+unsubscribe@googlegroups.com" target="_blank">bbr-dev+unsubscribe@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/bbr-dev/CAHb6LvrK_exkt_rbukYkF4_hwPXyy9T%2BZNGzdK79x91RrK49Mg%40mail.gmail.com?utm_medium=email&utm_source=footer" target="_blank">https://groups.google.com/d/msgid/bbr-dev/CAHb6LvrK_exkt_rbukYkF4_hwPXyy9T%2BZNGzdK79x91RrK49Mg%40mail.gmail.com</a>.<br>
</blockquote></div></div>