Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] a data point on syn and dscp
Date: Tue, 9 Mar 2021 10:58:25 -0800	[thread overview]
Message-ID: <CAA93jw44H-uB+x=qhjQrBPL58JXxV2zPL93dKCbW_iZMxgwZRg@mail.gmail.com> (raw)

I have been noticing some syn packets get marked AF21 in transit. I
haven't looked into it hard as yet,
but it might be a useful statistic to be collecting from various vantage points.

secondly, I am under the impression that linux now paces even the
initial iw based on the syn/ack pairb,
but haven't tracked it very much. Is this true? I haven't built a
kernel in ages, nor reviewed git logs. Trying to get on it now.

Now, I don't mind if the syn or syn/ack are getting prioritized very
much - delay in one direction
does not equal the delay in the other, but it does lead to a slight
mis-estimate as to how to fill the pipe
with that initial burst being prioritized outside the main fifo.
(fq_codel of course, essentially offers
zero delay and a correct estimate of the length of the pipe for both
kinds of packet)

this leads to my final question in that early sce and l4s experiments
did have a lot of trouble with having to pace the initial burst, and I
don't know what is actually done there, now, in current oses.

-- 
"For a successful technology, reality must take precedence over public
relations, for Mother Nature cannot be fooled" - Richard Feynman

dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729

             reply	other threads:[~2021-03-09 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 18:58 Dave Taht [this message]
2021-03-10  8:22 ` [Ecn-sane] SCE pacing (was: a data point on syn and dscp) Pete Heist

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw44H-uB+x=qhjQrBPL58JXxV2zPL93dKCbW_iZMxgwZRg@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox