Revision ecd9c5cd46e013659e2fad433057bad1ba66888e authored by Yevgeny Kliteynik on 29 December 2021, 20:22:05 UTC, committed by Saeed Mahameed on 24 February 2022, 00:08:11 UTC
When deciding whether to start syncing and actually free all the "hot"
ICM chunks, we need to consider the type of the ICM chunks that we're
dealing with. For instance, the amount of available ICM for MODIFY_ACTION
is significantly lower than the usual STE ICM, so the threshold should
account for that - otherwise we can deplete MODIFY_ACTION memory just by
creating and deleting the same modify header action in a continuous loop.
This patch replaces the hard-coded threshold with a dynamic value.
Fixes: 1c58651412bb ("net/mlx5: DR, ICM memory pools sync optimization")
Signed-off-by: Yevgeny Kliteynik <kliteyn@nvidia.com>
Reviewed-by: Alex Vesker <valex@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
1 parent ffb0753
| File | Mode | Size |
|---|---|---|
| apparmor | ||
| bpf | ||
| integrity | ||
| keys | ||
| landlock | ||
| loadpin | ||
| lockdown | ||
| safesetid | ||
| selinux | ||
| smack | ||
| tomoyo | ||
| yama | ||
| Kconfig | -rw-r--r-- | 10.3 KB |
| Kconfig.hardening | -rw-r--r-- | 10.8 KB |
| Makefile | -rw-r--r-- | 892 bytes |
| commoncap.c | -rw-r--r-- | 43.0 KB |
| device_cgroup.c | -rw-r--r-- | 21.1 KB |
| inode.c | -rw-r--r-- | 10.6 KB |
| lsm_audit.c | -rw-r--r-- | 10.9 KB |
| min_addr.c | -rw-r--r-- | 1.3 KB |
| security.c | -rw-r--r-- | 66.0 KB |
Computing file changes ...
