| 12345678910111213141516171819202122232425262728293031323334353637383940 |
- From d7936f11aded13f03871c0d6502d611d6a1e2dc5 Mon Sep 17 00:00:00 2001
- Message-Id: <d7936f11aded13f03871c0d6502d611d6a1e2dc5.1659815468.git.chunkeey@gmail.com>
- In-Reply-To: <53b5c5f559cc95fc676cb4cc9e5a8d9f0cb8f58c.1659815468.git.chunkeey@gmail.com>
- References: <53b5c5f559cc95fc676cb4cc9e5a8d9f0cb8f58c.1659815468.git.chunkeey@gmail.com>
- From: Christian Lamparter <[email protected]>
- Date: Sat, 6 Aug 2022 19:27:20 +0200
- Subject: [PATCH v1 2/2] um: increase default virtual physical memory to 64 MiB
- To: [email protected]
- Cc: Richard Weinberger <[email protected]>,
- Anton Ivanov <[email protected]>,
- Johannes Berg <[email protected]>
- The current 32 MiB of RAM causes OOMs to appear shortly after
- booting in a minimal OpenWrt 22.03 configuration with a
- 5.10.134 kernel.
- Of course, passing a "mem=64M" (from the --help text) parameter
- works too, but it produces the following (info) message:
- | [ 0.000000] Unknown kernel command line parameters "mem=64M", will be passed to user space.
- That's why, I think it would be nicer, if this is working out
- of the box again :).
- Signed-off-by: Christian Lamparter <[email protected]>
- ---
- arch/um/kernel/um_arch.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
- --- a/arch/um/kernel/um_arch.c
- +++ b/arch/um/kernel/um_arch.c
- @@ -130,7 +130,7 @@ static int have_root __initdata;
- static int have_console __initdata;
-
- /* Set in uml_mem_setup and modified in linux_main */
- -long long physmem_size = 32 * 1024 * 1024;
- +long long physmem_size = 64 * 1024 * 1024;
- EXPORT_SYMBOL(physmem_size);
-
- static const char *usage_string =
|
