diff options
| author | Paul Menzel <pmenzel@molgen.mpg.de> | 2020-08-11 12:29:23 +0300 |
|---|---|---|
| committer | Petr Mladek <pmladek@suse.com> | 2020-11-03 11:34:40 +0300 |
| commit | 0f7636e1654338c34e3c220c02b2ffad78b6ccc0 (patch) | |
| tree | 91f98c59bdc35b0b0f849c2fdfd1959f5bb8e1c0 /mm/vmscan.c | |
| parent | 8119c4332d253660e0a6b8748fe0749961cfbc97 (diff) | |
| download | linux-0f7636e1654338c34e3c220c02b2ffad78b6ccc0.tar.xz | |
init/Kconfig: Fix CPU number in LOG_CPU_MAX_BUF_SHIFT description
Currently, LOG_BUF_SHIFT defaults to 17, which is 2 ^ 17 bytes = 128 KB,
and LOG_CPU_MAX_BUF_SHIFT defaults to 12, which is 2 ^ 12 bytes = 4 KB.
Half of 128 KB is 64 KB, so more than 16 CPUs are required for the value
to be used, as then the sum of contributions is greater than 64 KB for
the first time. My guess is, that the description was written with the
configuration values used in the SUSE in mind.
Fixes: 23b2899f7f194f06e ("printk: allow increasing the ring buffer depending on the number of CPUs")
Cc: Luis R. Rodriguez <mcgrof@suse.com>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de>
Reviewed-by: Petr Mladek <pmladek@suse.com>
Signed-off-by: Petr Mladek <pmladek@suse.com>
Link: https://lore.kernel.org/r/20200811092924.6256-1-pmenzel@molgen.mpg.de
Diffstat (limited to 'mm/vmscan.c')
0 files changed, 0 insertions, 0 deletions