From: Florian Westphal <fw@strlen.de>
To: <netdev@vger.kernel.org>
Subject: [PATCH -next 0/3] tcp: receive-side per route dctcp handling
Date: Fri, 28 Aug 2015 14:11:06 +0200 [thread overview]
Message-ID: <1440763869-23067-1-git-send-email-fw@strlen.de> (raw)
Currently, the following case doesn't use DCTCP, even if it should:
- responder has f.e. cubic as system wide default
- 'ip route congctl dctcp $src' was set
Then, DCTCP is NOT used if a DCTCP sender attempts to connect from a
host in the $src range: ECT(0) is set, but listen_sk is not dctcp, so we
fail the INET_ECN_is_not_ect sanity check.
We also have to examine the dst used for the SYN/ACK reply to make this
case work.
In order to minimize additional cost, store the 'ecn is must have'
information is the dst_features field.
The set targets -next instead of -net since this doesn't seem to be a
serious bug and to give the change more soak time until it hits linus tree.
Daniel Borkmann (2):
net: fib6: reduce identation in ip6_convert_metrics
tcp: use dctcp if enabled on the route to the initiator
Florian Westphal (1):
net: fib: move metrics parsing to a helper
include/net/tcp.h | 2 +-
include/uapi/linux/rtnetlink.h | 11 +++---
net/core/rtnetlink.c | 4 +++
net/ipv4/fib_semantics.c | 78 ++++++++++++++++++++++++++----------------
net/ipv4/tcp_cong.c | 9 +++--
net/ipv4/tcp_input.c | 7 ++--
net/ipv6/route.c | 39 ++++++++++++---------
7 files changed, 94 insertions(+), 56 deletions(-)
next reply other threads:[~2015-08-28 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 12:11 Florian Westphal [this message]
2015-08-28 12:11 ` [PATCH -next 1/3] net: fib: move metrics parsing to a helper Florian Westphal
2015-08-28 12:11 ` [PATCH -next 2/3] net: fib6: reduce identation in ip6_convert_metrics Florian Westphal
2015-08-28 12:11 ` [PATCH -next 3/3] tcp: use dctcp if enabled on the route to the initiator Florian Westphal
2015-08-28 21:18 ` David Miller
2015-08-29 20:51 ` Daniel Borkmann
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=1440763869-23067-1-git-send-email-fw@strlen.de \
--to=fw@strlen.de \
--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 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).