Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933780AbbBQK7w (ORCPT ); Tue, 17 Feb 2015 05:59:52 -0500 Received: from mx1.redhat.com ([209.132.183.28]:56850 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933682AbbBQK7v (ORCPT ); Tue, 17 Feb 2015 05:59:51 -0500 Message-ID: <54E31F24.1060705@redhat.com> Date: Tue, 17 Feb 2015 11:59:48 +0100 From: Paolo Bonzini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: "Michael S. Tsirkin" , Igor Mammedov CC: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH] vhost: support upto 509 memory regions References: <1423842599-5174-1-git-send-email-imammedo@redhat.com> <20150217090242.GA20254@redhat.com> In-Reply-To: <20150217090242.GA20254@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 670 Lines: 23 On 17/02/2015 10:02, Michael S. Tsirkin wrote: > > Increasing VHOST_MEMORY_MAX_NREGIONS from 65 to 509 > > to match KVM_USER_MEM_SLOTS fixes issue for vhost-net. > > > > Signed-off-by: Igor Mammedov > > This scares me a bit: each region is 32byte, we are talking > a 16K allocation that userspace can trigger. What's bad with a 16K allocation? > How does kvm handle this issue? It doesn't. Paolo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/