From: Eric Dumazet <edumazet@google.com>
To: chia-yu.chang@nokia-bell-labs.com
Cc: pabeni@redhat.com, linux-doc@vger.kernel.org, corbet@lwn.net,
horms@kernel.org, dsahern@kernel.org, kuniyu@amazon.com,
bpf@vger.kernel.org, netdev@vger.kernel.org,
dave.taht@gmail.com, jhs@mojatatu.com, kuba@kernel.org,
stephen@networkplumber.org, xiyou.wangcong@gmail.com,
jiri@resnulli.us, davem@davemloft.net, andrew+netdev@lunn.ch,
donald.hunter@gmail.com, ast@fiberby.net, liuhangbin@gmail.com,
shuah@kernel.org, linux-kselftest@vger.kernel.org,
ij@kernel.org, ncardwell@google.com,
koen.de_schepper@nokia-bell-labs.com, g.white@cablelabs.com,
ingemar.s.johansson@ericsson.com, mirja.kuehlewind@ericsson.com,
cheshire@apple.com, rs.ietf@gmx.at, Jason_Livingood@comcast.com,
vidhi_goel@apple.com
Subject: Re: [PATCH v15 net-next 14/14] tcp: accecn: try to fit AccECN option with SACK
Date: Thu, 21 Aug 2025 06:04:20 -0700 [thread overview]
Message-ID: <CANn89iLFEM+mbU2d0AEH3O+3zg5Cwm7pdmaadUxXifUqLuaQLg@mail.gmail.com> (raw)
In-Reply-To: <20250815083930.10547-15-chia-yu.chang@nokia-bell-labs.com>
On Fri, Aug 15, 2025 at 1:40 AM <chia-yu.chang@nokia-bell-labs.com> wrote:
>
> From: Chia-Yu Chang <chia-yu.chang@nokia-bell-labs.com>
>
> As SACK blocks tend to eat all option space when there are
> many holes, it is useful to compromise on sending many SACK
> blocks in every ACK and attempt to fit the AccECN option
> there by reducing the number of SACK blocks. However, it will
> never go below two SACK blocks because of the AccECN option.
>
> As the AccECN option is often not put to every ACK, the space
> hijack is usually only temporary. Depending on the reuqired
> AccECN fields (can be either 3, 2, 1, or 0, cf. Table 5 in
> AccECN spec) and the NOPs used for alignment of other
> TCP options, up to two SACK blocks will be reduced. Please
> find below tables for more details:
>
> +====================+=========================================+
> | Number of | Required | Remaining | Number of | Final |
> | SACK | AccECN | option | reduced | number of |
> | blocks | fields | spaces | SACK blocks | SACK blocks |
> +===========+==========+===========+=============+=============+
> | x (<=2) | 0 to 3 | any | 0 | x |
> +-----------+----------+-----------+-------------+-------------+
> | 3 | 0 | any | 0 | 3 |
> | 3 | 1 | <4 | 1 | 2 |
> | 3 | 1 | >=4 | 0 | 3 |
> | 3 | 2 | <8 | 1 | 2 |
> | 3 | 2 | >=8 | 0 | 3 |
> | 3 | 3 | <12 | 1 | 2 |
> | 3 | 3 | >=12 | 0 | 3 |
> +-----------+----------+-----------+-------------+-------------+
> | y (>=4) | 0 | any | 0 | y |
> | y (>=4) | 1 | <4 | 1 | y-1 |
> | y (>=4) | 1 | >=4 | 0 | y |
> | y (>=4) | 2 | <8 | 1 | y-1 |
> | y (>=4) | 2 | >=8 | 0 | y |
> | y (>=4) | 3 | <4 | 2 | y-2 |
> | y (>=4) | 3 | <12 | 1 | y-1 |
> | y (>=4) | 3 | >=12 | 0 | y |
> +===========+==========+===========+=============+=============+
>
It is unclear if this chart takes into account the TCP TS option ?
Can you clarify this point ?
next prev parent reply other threads:[~2025-08-21 13:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 8:39 [PATCH v15 net-next 00/14] AccECN protocol patch series chia-yu.chang
2025-08-15 8:39 ` [PATCH v15 net-next 01/14] tcp: reorganize SYN ECN code chia-yu.chang
2025-08-15 8:39 ` [PATCH v15 net-next 02/14] tcp: fast path functions later chia-yu.chang
2025-08-15 8:39 ` [PATCH v15 net-next 03/14] tcp: reorganize tcp_sock_write_txrx group for variables later chia-yu.chang
2025-08-15 8:39 ` [PATCH v15 net-next 04/14] tcp: ecn functions in separated include file chia-yu.chang
2025-08-21 8:53 ` Eric Dumazet
2025-08-15 8:39 ` [PATCH v15 net-next 05/14] tcp: AccECN core chia-yu.chang
2025-08-15 8:39 ` [PATCH v15 net-next 06/14] tcp: accecn: AccECN negotiation chia-yu.chang
2025-08-21 12:22 ` Eric Dumazet
2025-08-15 8:39 ` [PATCH v15 net-next 07/14] tcp: accecn: add AccECN rx byte counters chia-yu.chang
2025-08-21 8:57 ` Eric Dumazet
2025-08-15 8:39 ` [PATCH v15 net-next 08/14] tcp: accecn: AccECN needs to know delivered bytes chia-yu.chang
2025-08-21 12:24 ` Eric Dumazet
2025-08-21 14:33 ` Chia-Yu Chang (Nokia)
2025-08-15 8:39 ` [PATCH v15 net-next 09/14] tcp: sack option handling improvements chia-yu.chang
2025-08-15 8:39 ` [PATCH v15 net-next 10/14] tcp: accecn: AccECN option chia-yu.chang
2025-08-21 12:29 ` Eric Dumazet
2025-08-21 14:58 ` Chia-Yu Chang (Nokia)
2025-08-21 17:32 ` Ilpo Järvinen
2025-08-21 17:46 ` Eric Dumazet
2025-09-02 12:23 ` Chia-Yu Chang (Nokia)
2025-08-15 8:39 ` [PATCH v15 net-next 11/14] tcp: accecn: AccECN option send control chia-yu.chang
2025-08-21 12:46 ` Eric Dumazet
2025-08-15 8:39 ` [PATCH v15 net-next 12/14] tcp: accecn: AccECN option failure handling chia-yu.chang
2025-08-21 12:55 ` Eric Dumazet
2025-08-22 10:00 ` Chia-Yu Chang (Nokia)
2025-08-15 8:39 ` [PATCH v15 net-next 13/14] tcp: accecn: AccECN option ceb/cep and ACE field multi-wrap heuristics chia-yu.chang
2025-08-15 8:39 ` [PATCH v15 net-next 14/14] tcp: accecn: try to fit AccECN option with SACK chia-yu.chang
2025-08-21 13:04 ` Eric Dumazet [this message]
2025-08-22 10:08 ` Chia-Yu Chang (Nokia)
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANn89iLFEM+mbU2d0AEH3O+3zg5Cwm7pdmaadUxXifUqLuaQLg@mail.gmail.com \
--to=edumazet@google.com \
--cc=Jason_Livingood@comcast.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@fiberby.net \
--cc=bpf@vger.kernel.org \
--cc=cheshire@apple.com \
--cc=chia-yu.chang@nokia-bell-labs.com \
--cc=corbet@lwn.net \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=g.white@cablelabs.com \
--cc=horms@kernel.org \
--cc=ij@kernel.org \
--cc=ingemar.s.johansson@ericsson.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=koen.de_schepper@nokia-bell-labs.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=mirja.kuehlewind@ericsson.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rs.ietf@gmx.at \
--cc=shuah@kernel.org \
--cc=stephen@networkplumber.org \
--cc=vidhi_goel@apple.com \
--cc=xiyou.wangcong@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).