All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: fw@strlen.de, netdev@vger.kernel.org,
	Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next v2 0/4] tcp: receive-side per route dctcp handling
Date: Mon, 31 Aug 2015 15:58:43 +0200	[thread overview]
Message-ID: <cover.1441027533.git.daniel@iogearbox.net> (raw)

Original cover letter:

  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.

v1 -> v2:
 - Addressed Dave's feedback, not exposing any bits to user space
 - Added patch 3 to reject incorrect configurations
 - Rest as is, rebased and retested

Thanks!

Daniel Borkmann (3):
  net: fib6: reduce identation in ip6_convert_metrics
  fib, fib6: reject invalid feature bits
  tcp: use dctcp if enabled on the route to the initiator

Florian Westphal (1):
  net: fib: move metrics parsing to a helper

 include/net/dst.h              |  6 ++++
 include/net/tcp.h              |  2 +-
 include/uapi/linux/rtnetlink.h | 11 +++---
 net/core/rtnetlink.c           |  6 ++++
 net/ipv4/fib_semantics.c       | 77 ++++++++++++++++++++++++++----------------
 net/ipv4/tcp_cong.c            |  9 +++--
 net/ipv4/tcp_input.c           |  7 ++--
 net/ipv6/route.c               | 39 ++++++++++++---------
 8 files changed, 101 insertions(+), 56 deletions(-)

-- 
1.9.3

             reply	other threads:[~2015-08-31 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 13:58 Daniel Borkmann [this message]
2015-08-31 13:58 ` [PATCH net-next v2 1/4] net: fib: move metrics parsing to a helper Daniel Borkmann
2015-08-31 13:58 ` [PATCH net-next v2 2/4] net: fib6: reduce identation in ip6_convert_metrics Daniel Borkmann
2015-08-31 13:58 ` [PATCH net-next v2 3/4] fib, fib6: reject invalid feature bits Daniel Borkmann
2015-08-31 13:58 ` [PATCH net-next v2 4/4] tcp: use dctcp if enabled on the route to the initiator Daniel Borkmann
2015-08-31 19:34 ` [PATCH net-next v2 0/4] tcp: receive-side per route dctcp handling David Miller

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=cover.1441027533.git.daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=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 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.