Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCHv4\s+net\-next\s+02\/14\]\s+ipvs\:\s+make\s+ip_vs_svc_table\s+and\s+ip_vs_svc_fwm

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCHv4\s+net\-next\s+02\/14\]\s+ipvs\:\s+make\s+ip_vs_svc_table\s+and\s+ip_vs_svc_fwm_table\s+per\s+netns\s*$/: 1 ]

Total 1 documents matching your query.

1. [PATCHv4 net-next 02/14] ipvs: make ip_vs_svc_table and ip_vs_svc_fwm_table per netns (score: 1): Author: Julian Anastasov <ja@xxxxxx>; Date: Tue, 28 May 2024 11:02:22 +0300; Current ipvs uses one global mutex "__ip_vs_mutex" to keep the global "ip_vs_svc_table" and "ip_vs_svc_fwm_table" safe. But when there are tens of thousands of services from different netns in the ta; /html/lvs-devel/2024-05/msg00056.html (36,947 bytes)

Current List: 1 - 1
Page: [1]