From: Alexandre Derumier <aderumier@odiso.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stefan Reiter <s.reiter@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-kernel] add patch: vhost: bump max_mem_regions to 509
Date: Tue, 17 Nov 2020 11:53:59 +0100 [thread overview]
Message-ID: <CAMGxVzB_1UCJGmqzAQYFXFCxpCNTj9bC+Z79G2aTZPbKEtxaCg@mail.gmail.com> (raw)
In-Reply-To: <d02a361f-1e5b-3340-77ad-178a6e042dec@proxmox.com>
>>What is wrong with setting it as module option?
Nothing wrong. in 2016, Dietmar wanted it in kernel. (don't remember,
maybe the module option didn't exist at this time)
>>above hunk for the submodule shouldn't be included in the patch, it refers to
>>a git object which is not in ubuntus tree, probably only local in your working
>>tree.
oops, sorry.
Do you prefer a module option file ?
Le lun. 16 nov. 2020 à 11:25, Thomas Lamprecht
<t.lamprecht@proxmox.com> a écrit :
>
> On 15.11.20 19:36, Alexandre Derumier wrote:
> > 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
> >
>
> What is wrong with setting it as module option?
> https://lists.proxmox.com/pipermail/pve-devel/2016-December/024508.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.
> >
> >
>
> maybe Stefan gets around to make this all a nicer approach?
>
> https://lists.proxmox.com/pipermail/pve-devel/2016-December/024519.html
>
> >
> > 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
> snip
> > 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
> >
>
> above hunk for the submodule shouldn't be included in the patch, it refers to
> a git object which is not in ubuntus tree, probably only local in your working
> tree.
>
>
prev parent reply other threads:[~2020-11-17 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 18:36 Alexandre Derumier
2020-11-16 6:38 ` Alexandre Derumier
2020-11-16 10:25 ` Thomas Lamprecht
2020-11-17 10:53 ` Alexandre Derumier [this message]
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=CAMGxVzB_1UCJGmqzAQYFXFCxpCNTj9bC+Z79G2aTZPbKEtxaCg@mail.gmail.com \
--to=aderumier@odiso.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.reiter@proxmox.com \
--cc=t.lamprecht@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