From: Ido Schimmel <idosch@idosch.org>
To: David Ahern <dsahern@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, idosch@mellanox.com,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH v4 net-next 1/3] ipv4: Move cached routes to fib_nh_common
Date: Tue, 30 Apr 2019 17:56:37 +0300 [thread overview]
Message-ID: <20190430145637.GA20908@splinter> (raw)
In-Reply-To: <20190430144550.15033-2-dsahern@kernel.org>
On Tue, Apr 30, 2019 at 07:45:48AM -0700, David Ahern wrote:
> From: David Ahern <dsahern@gmail.com>
>
> While the cached routes, nh_pcpu_rth_output and nh_rth_input, are IPv4
> specific, a later patch wants to make them accessible for IPv6 nexthops
> with IPv4 routes using a fib6_nh. Move the cached routes from fib_nh to
> fib_nh_common and update references.
>
> Initialization of the cached entries is moved to fib_nh_common_init,
> and free is moved to fib_nh_common_release.
>
> Change in location only, from fib_nh up to fib_nh_common; no functional
> change intended.
>
> Signed-off-by: David Ahern <dsahern@gmail.com>
Reviewed-by: Ido Schimmel <idosch@mellanox.com>
next prev parent reply other threads:[~2019-04-30 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 14:45 [PATCH v4 net-next 0/3] ipv4: Move location of pcpu route cache and exceptions David Ahern
2019-04-30 14:45 ` [PATCH v4 net-next 1/3] ipv4: Move cached routes to fib_nh_common David Ahern
2019-04-30 14:56 ` Ido Schimmel [this message]
2019-04-30 14:45 ` [PATCH v4 net-next 2/3] ipv4: Pass fib_nh_common to rt_cache_route David Ahern
2019-04-30 14:45 ` [PATCH v4 net-next 3/3] ipv4: Move exception bucket to nh_common David Ahern
2019-05-05 7:47 ` [PATCH v4 net-next 0/3] ipv4: Move location of pcpu route cache and exceptions 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=20190430145637.GA20908@splinter \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=idosch@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 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.