From: Eric Dumazet <eric.dumazet@gmail.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: [PATCH net-next 0/2] net/sched: implement L4S style ce_threshold_ect1 marking
Date: Thu, 14 Oct 2021 10:59:16 -0700 [thread overview]
Message-ID: <20211014175918.60188-1-eric.dumazet@gmail.com> (raw)
From: Eric Dumazet <edumazet@google.com>
As suggested by Ingemar Johansson, Neal Cardwell, and others, fq_codel can be used
for Low Latency, Low Loss, Scalable Throughput (L4S) with a small change.
In ce_threshold_ect1 mode, only ECT(1) packets can be marked to CE if
their sojourn time is above the threshold.
Eric Dumazet (2):
net: add skb_get_dsfield() helper
fq_codel: implement L4S style ce_threshold_ect1 marking
include/net/codel.h | 2 ++
include/net/codel_impl.h | 18 +++++++++++++++---
include/net/inet_ecn.h | 17 +++++++++++++++++
include/uapi/linux/pkt_sched.h | 1 +
net/mac80211/sta_info.c | 1 +
net/sched/sch_fq_codel.c | 15 +++++++++++----
6 files changed, 47 insertions(+), 7 deletions(-)
--
2.33.0.1079.g6e70778dc9-goog
next reply other threads:[~2021-10-14 17:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 17:59 Eric Dumazet [this message]
2021-10-14 17:59 ` [PATCH net-next 1/2] net: add skb_get_dsfield() helper Eric Dumazet
2021-10-14 17:59 ` [PATCH net-next 2/2] fq_codel: implement L4S style ce_threshold_ect1 marking Eric Dumazet
2021-10-14 19:54 ` Toke Høiland-Jørgensen
2021-10-14 21:35 ` Eric Dumazet
2021-10-14 23:24 ` Toke Høiland-Jørgensen
2021-10-16 7:39 ` Jonathan Morton
2021-10-17 11:22 ` Bob Briscoe
2021-10-17 12:18 ` Jonathan Morton
2021-10-18 19:43 ` Gorry Fairhurst
2021-10-15 12:59 ` Bob Briscoe
2021-10-15 14:08 ` Eric Dumazet
2021-10-15 15:49 ` Neal Cardwell
2021-10-17 0:42 ` Bob Briscoe
2021-10-18 11:42 ` Dave Taht
2021-10-15 10:40 ` [PATCH net-next 0/2] net/sched: " patchwork-bot+netdevbpf
2021-10-15 13:01 ` Toke Høiland-Jørgensen
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=20211014175918.60188-1-eric.dumazet@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.