From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] Fwd: [RFC PATCH 00/28]: Accurate ECN for TCP
Date: Thu, 19 Mar 2020 15:21:28 -0700 [thread overview]
Message-ID: <CAA93jw5LUwM-mo4wq7Z2JDKsrOH-NrxwsX3ksHATnYnoYBgyKg@mail.gmail.com> (raw)
In-Reply-To: <1584524612-24470-1-git-send-email-ilpo.jarvinen@helsinki.fi>
I have no comments to make, aside from my concerns with dealing
correctly with offload engines.
---------- Forwarded message ---------
From: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
Date: Wed, Mar 18, 2020 at 2:45 AM
Subject: [RFC PATCH 00/28]: Accurate ECN for TCP
To: <netdev@vger.kernel.org>
Cc: Yuchung Cheng <ycheng@google.com>, Neal Cardwell
<ncardwell@google.com>, Eric Dumazet <eric.dumazet@gmail.com>, Olivier
Tilmans <olivier.tilmans@nokia-bell-labs.com>
Hi all,
Here's the full Accurate ECN implementation mostly based on
https://tools.ietf.org/html/draft-ietf-tcpm-accurate-ecn-11
Comments would be highly appreciated. The GSO/TSO maze of bits
in particular is something I'm somewhat unsure if I got it
right (for a feature that has a software fallback).
There is an extensive set of packetdrill unit tests for most of
the functionality (I'll send separately to packetdrill).
Please note that this submission is not yet intented to be
included to net-next because some small changes seem still
possible to the spec.
Documentation/networking/ip-sysctl.txt | 12 +-
drivers/net/tun.c | 3 +-
include/linux/netdev_features.h | 3 +
include/linux/skbuff.h | 2 +
include/linux/tcp.h | 19 ++
include/net/tcp.h | 221 ++++++++++---
include/uapi/linux/tcp.h | 9 +-
net/ethtool/common.c | 1 +
net/ipv4/bpf_tcp_ca.c | 2 +-
net/ipv4/syncookies.c | 12 +
net/ipv4/tcp.c | 10 +-
net/ipv4/tcp_dctcp.c | 2 +-
net/ipv4/tcp_dctcp.h | 2 +-
net/ipv4/tcp_input.c | 558 ++++++++++++++++++++++++++++-----
net/ipv4/tcp_ipv4.c | 8 +-
net/ipv4/tcp_minisocks.c | 84 ++++-
net/ipv4/tcp_offload.c | 11 +-
net/ipv4/tcp_output.c | 298 +++++++++++++++---
net/ipv4/tcp_timer.c | 4 +-
net/ipv6/syncookies.c | 1 +
net/ipv6/tcp_ipv6.c | 4 +-
net/netfilter/nf_log_common.c | 4 +-
--
i.
ps. My apologies if you got a duplicate copy of them. It seems that
answering "no" to git send-email asking "Send this email?" might
still have sent something out.
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next parent reply other threads:[~2020-03-19 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1584524612-24470-1-git-send-email-ilpo.jarvinen@helsinki.fi>
2020-03-19 22:21 ` Dave Taht [this message]
[not found] ` <1584524612-24470-10-git-send-email-ilpo.jarvinen@helsinki.fi>
[not found] ` <6940af98-7083-15c7-dcea-54eb9d040a3d@gmail.com>
[not found] ` <alpine.DEB.2.20.2003192233580.5256@whs-18.cs.helsinki.fi>
2020-03-19 23:12 ` [Ecn-sane] Fwd: [RFC PATCH 09/28] gso: AccECN support Dave Taht
[not found] ` <1584524612-24470-29-git-send-email-ilpo.jarvinen@helsinki.fi>
[not found] ` <CAA93jw7_YG-KMns8UP-aTPHNjPG+A_rwWUWbt1+8i4+UNhALnA@mail.gmail.com>
[not found] ` <alpine.DEB.2.20.2003202348250.21767@whs-18.cs.helsinki.fi>
2020-03-21 2:46 ` [Ecn-sane] Fwd: [RFC PATCH 28/28] tcp: AccECN sysctl documentation Dave Taht
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=CAA93jw5LUwM-mo4wq7Z2JDKsrOH-NrxwsX3ksHATnYnoYBgyKg@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