[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3e8f39e2-ef6d-485d-9a39-a36b04266a62@gmail.com>
Date: Wed, 3 Apr 2024 13:50:21 +0200
From: Leone Fernando <leone4fernando@...il.com>
To: David Ahern <dsahern@...nel.org>, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, willemb@...gle.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 0/4] net: route: improve route hinting
Hi David,
>
> For the rest of it, Jakub's response was a good summary: it is hard to
> know if there is a benefit to real workloads. Cache's consume resources
> (memory and cpu) and will be wrong some percentage of the time
> increasing overhead.
>
I understand what you are saying here.
Do you have an idea for extra tests or measurements to make sure
the patch also improves in real workloads?
> Also, it is targeted at a very narrow use case -- IPv4 only, no custom
> FIB rules and no multipath.
Implementation for IPv6 is almost identical. I decided to start with IPv4
and I plan to submit IPv6 support in a future patch.
This patch basically improves the hinting mechanism that Paolo introduced
and it handles the same cases.
Adding support for FIB rules and multipath is a bit more complicated but
also possible. I am willing to keep working on this patch to meet the
remaining cases including IPv6.
Thanks,
Leone
Powered by blists - more mailing lists