Thanks @Julian Anastasov. I appreciate the detailed response around why these limits exist. Personally, I won't be able to own the task of making these checks more intelligent, but for now, I wonder
I see. This makes sense to me as RHEL 7 does not include the range check, while RHEL 8 and RHEL 9 both includes it. The reason why any number beyond 31 results in a lower number is to be searched in
Hello, Some 32-bit platforms have a 120MB limit for vmalloc. 24-bit table on 32-bit box will allocate 64MB. One way to solve the problem is to use in Kconfig: range 8 20 if !64BIT range 8 27 if 64BIT
Hi Simon, Andrea and Julian, I really appreciate you taking the time to respond to my patch. Some follow up questions that I'll appreciate a response for. @Simon Horman +1 to this. I wanted to add th
Hello, This is not a limit of number of connections. I prefer not to allow value above 24 without adding checks for the available memory, this more concern for 32-bit. Blindly allocating 2^20 (104857
Hi Abhijeet, for the record, RHEL ships with CONFIG_IP_VS_TAB_BITS set to 12 as default. Looks good to me. Reviewed-by: Andrea Claudi <aclaudi@xxxxxxxxxx>
Hi Abhijeet, 'The 20 bit (1m entries) ceiling exists since the original merge of ipvs in 2003, so likely this was just considered "big enough" back then.' Yes, that matches my recollection. There wer
Author: Abhijeet Rastogi via B4 Relay <devnull+abhijeet.1989.gmail.com@xxxxxxxxxx>
Date: Wed, 12 Apr 2023 13:49:08 -0700
Current range [8, 20] is set purely due to historical reasons because at the time, ~1M (2^20) was considered sufficient. Previous change regarding this limit is here. Link: https://lore.kernel.org/al