From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: netdev@vger.kernel.org, idosch@mellanox.com, mlxsw@mellanox.com,
dsahern@gmail.com
Subject: Re: [patch net-next 0/6] mlxsw: Align multipath hash parameters with kernel's
Date: Fri, 03 Nov 2017 15:41:03 +0900 (KST) [thread overview]
Message-ID: <20171103.154103.1599099649603916329.davem@davemloft.net> (raw)
In-Reply-To: <20171102161410.12171-1-jiri@resnulli.us>
From: Jiri Pirko <jiri@resnulli.us>
Date: Thu, 2 Nov 2017 17:14:04 +0100
> From: Jiri Pirko <jiri@mellanox.com>
>
> Ido says:
>
> This set makes sure the device is using the same parameters as the
> kernel when it computes the multipath hash during IP forwarding.
>
> First patch adds a new netevent to let interested listeners know that
> the multipath hash policy has changed.
>
> Next two patches do small and non-functional changes in the mlxsw
> driver.
>
> Last patches configure the multipath hash policy upon driver
> initialization and as a response to netevents.
Series applied, thanks everyone.
prev parent reply other threads:[~2017-11-03 6:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 16:14 [patch net-next 0/6] mlxsw: Align multipath hash parameters with kernel's Jiri Pirko
2017-11-02 16:14 ` [patch net-next 1/6] ipv4: Send a netevent whenever multipath hash policy is changed Jiri Pirko
2017-11-02 18:57 ` David Ahern
2017-11-02 16:14 ` [patch net-next 2/6] mlxsw: spectrum_router: Embed netevent notifier block in router struct Jiri Pirko
2017-11-02 16:14 ` [patch net-next 3/6] mlxsw: spectrum_router: Properly name netevent work struct Jiri Pirko
2017-11-02 16:14 ` [patch net-next 4/6] mlxsw: reg: Add Router ECMP Configuration Register Version 2 Jiri Pirko
2017-11-02 16:14 ` [patch net-next 5/6] mlxsw: spectrum_router: Align multipath hash parameters with kernel's Jiri Pirko
2017-11-02 16:14 ` [patch net-next 6/6] mlxsw: spectrum_router: Update multipath hash parameters upon netevents Jiri Pirko
2017-11-03 6:41 ` 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=20171103.154103.1599099649603916329.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=mlxsw@mellanox.com \
--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).