Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: wenxu@ucloud.cn
Cc: nikolay@cumulusnetworks.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4] route: Add multipath_hash in flowi_common to make user-define hash
Date: Wed, 27 Feb 2019 12:50:35 -0800 (PST)	[thread overview]
Message-ID: <20190227.125035.173565847969024167.davem@davemloft.net> (raw)
In-Reply-To: <1550979380-6617-1-git-send-email-wenxu@ucloud.cn>

From: wenxu@ucloud.cn
Date: Sun, 24 Feb 2019 11:36:20 +0800

> From: wenxu <wenxu@ucloud.cn>
> 
> Current fib_multipath_hash_policy can make hash based on the L3 or
> L4. But it only work on the outer IP. So a specific tunnel always
> has the same hash value. But a specific tunnel may contain so many
> inner connections.
> 
> This patch provide a generic multipath_hash in floi_common. It can
> make a user-define hash which can mix with L3 or L4 hash.
> 
> Signed-off-by: wenxu <wenxu@ucloud.cn>

Applied to net-next, thanks.

      reply	other threads:[~2019-02-27 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24  3:36 [PATCH net-next v4] route: Add multipath_hash in flowi_common to make user-define hash wenxu
2019-02-27 20:50 ` 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=20190227.125035.173565847969024167.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=wenxu@ucloud.cn \
    /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