From: Igor Mammedov <imammedo@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: mst@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH v4 2/2] vhost: add max_mem_regions module parameter
Date: Thu, 16 Jul 2015 13:05:39 +0200 [thread overview]
Message-ID: <20150716130539.38729e67@nial.brq.redhat.com> (raw)
In-Reply-To: <1435842491-131872-3-git-send-email-imammedo@redhat.com>
On Thu, 2 Jul 2015 15:08:11 +0200
Igor Mammedov <imammedo@redhat.com> wrote:
> it became possible to use a bigger amount of memory
> slots, which is used by memory hotplug for
> registering hotplugged memory.
> However QEMU crashes if it's used with more than ~60
> pc-dimm devices and vhost-net enabled since host kernel
> in module vhost-net refuses to accept more than 64
> memory regions.
>
> Allow to tweak limit via max_mem_regions module paramemter
> with default value set to 64 slots.
Michael,
what was the reason not to rise default?
As much as I think I can't come up with one.
Making it as module option doesn't make much sense
since old userspace will crash on new kernels anyway
until admins learn that there is a module option
to rise limit.
Rising default limit on par with kvm's will help
to avoid those crashes and would allow to drop
not necessary option to reduce user confusion.
>
> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> ---
> drivers/vhost/vhost.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
> index 6488011..9a68e2e 100644
> --- a/drivers/vhost/vhost.c
> +++ b/drivers/vhost/vhost.c
> @@ -29,8 +29,12 @@
>
> #include "vhost.h"
>
> +static ushort max_mem_regions = 64;
> +module_param(max_mem_regions, ushort, 0444);
> +MODULE_PARM_DESC(max_mem_regions,
> + "Maximum number of memory regions in memory map. (default: 64)");
> +
> enum {
> - VHOST_MEMORY_MAX_NREGIONS = 64,
> VHOST_MEMORY_F_LOG = 0x1,
> };
>
> @@ -696,7 +700,7 @@ static long vhost_set_memory(struct vhost_dev *d, struct vhost_memory __user *m)
> return -EFAULT;
> if (mem.padding)
> return -EOPNOTSUPP;
> - if (mem.nregions > VHOST_MEMORY_MAX_NREGIONS)
> + if (mem.nregions > max_mem_regions)
> return -E2BIG;
> newmem = vhost_kvzalloc(size + mem.nregions * sizeof(*m->regions));
> if (!newmem)
next prev parent reply other threads:[~2015-07-16 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 13:08 [PATCH v4 0/2] vhost: support more than 64 memory regions Igor Mammedov
2015-07-02 13:08 ` [PATCH v4 1/2] vhost: extend memory regions allocation to vmalloc Igor Mammedov
2015-07-13 18:15 ` [PATCH] vhost: fix build failure on SPARC Igor Mammedov
2015-07-13 20:19 ` Michael S. Tsirkin
2015-07-13 21:41 ` Igor Mammedov
2015-07-02 13:08 ` [PATCH v4 2/2] vhost: add max_mem_regions module parameter Igor Mammedov
2015-07-16 11:05 ` Igor Mammedov [this message]
2015-07-08 12:51 ` [PATCH v4 0/2] vhost: support more than 64 memory regions Igor Mammedov
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=20150716130539.38729e67@nial.brq.redhat.com \
--to=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.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;
as well as URLs for NNTP newsgroup(s).