From: David Miller <davem@davemloft.net>
To: jkbs@redhat.com
Cc: netdev@vger.kernel.org, hannes@stressinduktion.org,
nikolay@cumulusnetworks.com, tom@herbertland.com
Subject: Re: [PATCH net-next] ipv6: Add sysctl for per namespace flow label reflection
Date: Thu, 24 Aug 2017 18:05:53 -0700 (PDT) [thread overview]
Message-ID: <20170824.180553.1621054459411024798.davem@davemloft.net> (raw)
In-Reply-To: <20170823075541.26764-1-jkbs@redhat.com>
From: Jakub Sitnicki <jkbs@redhat.com>
Date: Wed, 23 Aug 2017 09:55:41 +0200
> Reflecting IPv6 Flow Label at server nodes is useful in environments
> that employ multipath routing to load balance the requests. As "IPv6
> Flow Label Reflection" standard draft [1] points out - ICMPv6 PTB error
> messages generated in response to a downstream packets from the server
> can be routed by a load balancer back to the original server without
> looking at transport headers, if the server applies the flow label
> reflection. This enables the Path MTU Discovery past the ECMP router in
> load-balance or anycast environments where each server node is reachable
> by only one path.
>
> Introduce a sysctl to enable flow label reflection per net namespace for
> all newly created sockets. Same could be earlier achieved only per
> socket by setting the IPV6_FL_F_REFLECT flag for the IPV6_FLOWLABEL_MGR
> socket option.
>
> [1] https://tools.ietf.org/html/draft-wang-6man-flow-label-reflection-01
>
> Signed-off-by: Jakub Sitnicki <jkbs@redhat.com>
Ok, applied.
prev parent reply other threads:[~2017-08-25 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 7:55 [PATCH net-next] ipv6: Add sysctl for per namespace flow label reflection Jakub Sitnicki
2017-08-25 1:05 ` David Miller [this message]
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=20170824.180553.1621054459411024798.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jkbs@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=tom@herbertland.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).