target/linux/uml/patches-5.15/104-um-increase-default-virtual-physical-memory-to-64.patch

   1 From d7936f11aded13f03871c0d6502d611d6a1e2dc5 Mon Sep 17 00:00:00 2001
   2 Message-Id: <d7936f11aded13f03871c0d6502d611d6a1e2dc5.1659815468.git.chunkeey@gmail.com>
   3 In-Reply-To: <53b5c5f559cc95fc676cb4cc9e5a8d9f0cb8f58c.1659815468.git.chunkeey@gmail.com>
   4 References: <53b5c5f559cc95fc676cb4cc9e5a8d9f0cb8f58c.1659815468.git.chunkeey@gmail.com>
   5 From: Christian Lamparter <chunkeey@gmail.com>
   6 Date: Sat, 6 Aug 2022 19:27:20 +0200
   7 Subject: [PATCH v1 2/2] um: increase default virtual physical memory to 64 MiB
   8 To: linux-um@lists.infradead.org
   9 Cc: Richard Weinberger <richard@nod.at>,
  10     Anton Ivanov <anton.ivanov@cambridgegreys.com>,
  11     Johannes Berg <johannes@sipsolutions.net>
  12
  13 The current 32 MiB of RAM causes OOMs to appear shortly after
  14 booting in a minimal OpenWrt 22.03 configuration with a
  15 5.10.134 kernel.
  16
  17 Of course, passing a "mem=64M" (from the --help text) parameter
  18 works too, but it produces the following (info) message:
  19
  20 | [    0.000000] Unknown kernel command line parameters "mem=64M", will be passed to user space.
  21
  22 That's why, I think it would be nicer, if this is working out
  23 of the box again :).
  24
  25 Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
  26 ---
  27  arch/um/kernel/um_arch.c | 2 +-
  28  1 file changed, 1 insertion(+), 1 deletion(-)
  29
  30 --- a/arch/um/kernel/um_arch.c
  31 +++ b/arch/um/kernel/um_arch.c
  32 @@ -131,7 +131,7 @@ static int have_root __initdata;
  33  static int have_console __initdata;
  34
  35  /* Set in uml_mem_setup and modified in linux_main */
  36 -long long physmem_size = 32 * 1024 * 1024;
  37 +long long physmem_size = 64 * 1024 * 1024;
  38  EXPORT_SYMBOL(physmem_size);
  39
  40  static const char *usage_string =