From 3cee8d7830d0161e3b3ed323123d106b99a835ab Mon Sep 17 00:00:00 2001
From: Frederic Lecaille <flecaille@haproxy.com>
Date: Tue, 26 Nov 2024 07:46:17 +0100
Subject: [PATCH] DOC: quic: Amend the pacing information about BBR.

BBR handles itself its own burst size (mentioned as send_quantum in BBR RFC).
---
 doc/configuration.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/configuration.txt b/doc/configuration.txt
index e5e8e100b..9a4a34ad2 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -17239,7 +17239,8 @@ quic-cc-algo { cubic | newreno | bbr | nocc }[(<args,...>)]
     around 1252 bytes, and that a typical receive buffer is 208kB or 170
     datagrams, so in order to keep the traffic smooth, bursts should only
     represent a small fraction of this value (between a few units to a few tens
-    at most). See above paragraph for more explanation.
+    at most). See above paragraph for more explanation. This parameter is
+    ignored by BBR.
 
   Example:
       # newreno congestion control algorithm