From: David Ahern <dsahern@gmail.com>
To: "Yi Yang (杨燚)-云服务集团" <yangyi01@inspur.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "nikolay@cumulusnetworks.com" <nikolay@cumulusnetworks.com>
Subject: Re: [PATCH] can current ECMP implementation support consistent hashing for next hop?
Date: Thu, 11 Jun 2020 12:27:06 -0600 [thread overview]
Message-ID: <8ff0c684-7d33-c785-94d7-c0e6f8b79d64@gmail.com> (raw)
In-Reply-To: <6f0bf0c31d634134a0bf4ed4dbf17f9c@inspur.com>
On 6/11/20 8:56 AM, Yi Yang (杨燚)-云服务集团 wrote:
> Hi, folks
>
> We need to use Linux ECMP to do active-active load balancer, but consistent hash is necessary because load balance node may be added or removed dynamically, so number of hash bucket is changeable, but we have to distribute flow to load balance node which is handling this flow and has current session state, I’m not sure if current Linux has implemented the algorithm in https://tools.ietf.org/html/rfc2992, anybody can confirm yes or no?
>
> I checked source code in https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/net/ipv4/fib_semantics.c#n2176, every next hop in fib has a upper_bound, fib_select_multipath just checks if hash value is greater than upper_bound of next hop and decide if it is selected next hop, so I don't think current linux has implemented consistent hash, please correct me if I'm wrong.
>
> Thank you all so much in advance and sincerely appreciate your help.
>
The kernel does not do resilient hashing, but I believe you can do it
from userspace by updating route entries - replacing nexthop entries as
LB's come and go.
Cumulus docs have a good description:
https://docs.cumulusnetworks.com/cumulus-linux/Layer-3/Equal-Cost-Multipath-Load-Sharing-Hardware-ECMP/#resilient-hashing
next prev parent reply other threads:[~2020-06-11 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 14:56 [PATCH] can current ECMP implementation support consistent hashing for next hop? Yi Yang (杨燚)-云服务集团
2020-06-11 18:27 ` David Ahern [this message]
2020-06-12 0:32 ` 答复: " Yi Yang (杨燚)-云服务集团
2020-06-12 4:36 ` David Ahern
2020-06-15 6:56 ` 答复: [vger.kernel.org代发]Re: " Yi Yang (杨燚)-云服务集团
2020-06-15 22:42 ` David Ahern
2020-06-16 0:29 ` 答复: " Yi Yang (杨燚)-云服务集团
2020-08-02 14:49 ` Ido Schimmel
2020-08-06 16:45 ` David Ahern
2020-08-08 18:40 ` Ido Schimmel
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=8ff0c684-7d33-c785-94d7-c0e6f8b79d64@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=yangyi01@inspur.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).