diff options
| author | Sergey Senozhatsky <senozhatsky@chromium.org> | 2026-03-11 11:42:46 +0300 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2026-04-05 23:53:24 +0300 |
| commit | 5004a27edba5987bd75fe84c40b1b486ffae8f99 (patch) | |
| tree | c455f08005dc0dfc60d71fac9d5cf39b049d99d1 /include | |
| parent | ed19b9d5504f3f7adb68ad8d8db96c390c8570e5 (diff) | |
| download | linux-5004a27edba5987bd75fe84c40b1b486ffae8f99.tar.xz | |
zram: drop ->num_active_comps
It's not entirely correct to use ->num_active_comps for max-prio limit, as
->num_active_comps just tells the number of configured algorithms, not the
max configured priority. For instance, in the following theoretical
example:
[lz4] [nil] [nil] [deflate]
->num_active_comps is 2, while the actual max-prio is 3.
Drop ->num_active_comps and use ZRAM_MAX_COMPS instead.
Link: https://lkml.kernel.org/r/20260311084312.1766036-4-senozhatsky@chromium.org
Signed-off-by: Sergey Senozhatsky <senozhatsky@chromium.org>
Suggested-by: Minchan Kim <minchan@kernel.org>
Cc: Brian Geffon <bgeffon@google.com>
Cc: gao xu <gaoxu2@honor.com>
Cc: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions
