From: Alexandre Derumier <aderumier@odiso.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-kernel] add patch: vhost: bump max_mem_regions to 509
Date: Sun, 15 Nov 2020 19:36:09 +0100 [thread overview]
Message-ID: <20201115183609.3022395-1-aderumier@odiso.com> (raw)
Currently, default value is 64, so qemu is limited to 64 hotplug dimm
original patch from 2015
https://patchwork.kernel.org/project/kvm/patch/1438180163-275465-3-git-send-email-imammedo@redhat.com/
We have discusted about this in 2016 (At this time some optimisations patches were missing)
https://lists.proxmox.com/pipermail/pve-devel/2016-December/024502.html
Also, this fix this bugzilla
https://bugzilla.proxmox.com/show_bug.cgi?id=1426
Wolfgang proposed to have explicit dimm module management, it could be great,
but for now this patch is fixed the current implemlentation.
Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
---
...08-vhost-bump-max_mem_regions-to-509.patch | 32 +++++++++++++++++++
submodules/ubuntu-focal | 2 +-
2 files changed, 33 insertions(+), 1 deletion(-)
create mode 100644 patches/kernel/0008-vhost-bump-max_mem_regions-to-509.patch
diff --git a/patches/kernel/0008-vhost-bump-max_mem_regions-to-509.patch b/patches/kernel/0008-vhost-bump-max_mem_regions-to-509.patch
new file mode 100644
index 0000000..f547b7d
--- /dev/null
+++ b/patches/kernel/0008-vhost-bump-max_mem_regions-to-509.patch
@@ -0,0 +1,32 @@
+From 721ac248403a4c7ea98c416fc28f22c0bfbbb63d Mon Sep 17 00:00:00 2001
+From: Alexandre Derumier <aderumier@odiso.com>
+Date: Sun, 15 Nov 2020 19:19:28 +0100
+Subject: [PATCH] vhost: bump max_mem_regions to 509
+
+Currently, default value is 64, so qemu is limited to 64 hotplug dimm
+
+Signed-off-by: Alexandre Derumier <aderumier@odiso.com>
+---
+ drivers/vhost/vhost.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
+index 36ca2cf419bf..1d3eae6555fa 100644
+--- a/drivers/vhost/vhost.c
++++ b/drivers/vhost/vhost.c
+@@ -33,10 +33,10 @@
+
+ #include "vhost.h"
+
+-static ushort max_mem_regions = 64;
++static ushort max_mem_regions = 509;
+ module_param(max_mem_regions, ushort, 0444);
+ MODULE_PARM_DESC(max_mem_regions,
+- "Maximum number of memory regions in memory map. (default: 64)");
++ "Maximum number of memory regions in memory map. (default: 509)");
+ static int max_iotlb_entries = 2048;
+ module_param(max_iotlb_entries, int, 0444);
+ MODULE_PARM_DESC(max_iotlb_entries,
+--
+2.20.1
+
diff --git a/submodules/ubuntu-focal b/submodules/ubuntu-focal
index fd386a6..721ac24 160000
--- a/submodules/ubuntu-focal
+++ b/submodules/ubuntu-focal
@@ -1 +1 @@
-Subproject commit fd386a64a1ed3f2f047318508ebd733f56a4fab2
+Subproject commit 721ac248403a4c7ea98c416fc28f22c0bfbbb63d
--
2.20.1
next reply other threads:[~2020-11-15 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 18:36 Alexandre Derumier [this message]
2020-11-16 6:38 ` Alexandre Derumier
2020-11-16 10:25 ` Thomas Lamprecht
2020-11-17 10:53 ` Alexandre Derumier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201115183609.3022395-1-aderumier@odiso.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox