Re: [PATCH] ipvs: Use flexible array for MH lookup table

Julian Anastasov <[email protected]> Fri, 22 May 2026 20:12:31 +0300 (EEST)
Newsgroups org.kernel.vger.lvs-devel,org.kernel.vger.linux-kernel,org.kernel.vger.netdev,org.kernel.vger.netfilter-devel
Message-ID <[email protected]>
	Hello,

On Mon, 18 May 2026, Rosen Penev wrote:

> Store the Maglev hash lookup table in the scheduler state
> allocation instead of allocating it separately.
> 
> This keeps the lookup table tied to the RCU-freed state lifetime and
> simplifies the allocation and cleanup paths.
> 
> Assisted-by: Codex:GPT-5.5
> Signed-off-by: Rosen Penev <[email protected]>

	Thanks for the efforts but it is better to keep the table 
allocated separately. As Sashiko [1] points out, the table size is
properly selected and we risk double-sized allocations if we apply
this patch.

	As for the problem in ip_vs_edit_service(), I have to
provide separate bugfix...

[1]:
https://sashiko.dev/#/patchset/20260519015506.634185-1-rosenp%40gmail.com

Regards

--
Julian Anastasov <[email protected]>