[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190618.094600.427814233009639292.davem@davemloft.net>
Date: Tue, 18 Jun 2019 09:46:00 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: idosch@...sch.org
Cc: netdev@...r.kernel.org, jiri@...lanox.com, dsahern@...il.com,
alexpe@...lanox.com, mlxsw@...lanox.com, idosch@...lanox.com
Subject: Re: [PATCH net-next v2 00/16] mlxsw: Improve IPv6 route insertion
rate
From: Ido Schimmel <idosch@...sch.org>
Date: Tue, 18 Jun 2019 18:12:42 +0300
> Unlike IPv4, an IPv6 multipath route in the kernel is composed from
> multiple sibling routes, each representing a single nexthop.
>
> Therefore, an addition of a multipath route with N nexthops translates
> to N in-kernel notifications. This is inefficient for device drivers
> that need to program the route to the underlying device. Each time a new
> nexthop is appended, a new nexthop group needs to be constructed and the
> old one deleted.
>
> This patchset improves the situation by sending a single notification
> for a multipath route addition / deletion instead of one per-nexthop.
> When adding thousands of multipath routes with 16 nexthops, I measured
> an improvement of about x10 in the insertion rate.
...
Series applied, thanks everyone.
Powered by blists - more mailing lists