From owner-svn-src-all@FreeBSD.ORG Wed Jun 25 13:50:10 2014 Return-Path: Delivered-To: svn-src-all@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 071962B5; Wed, 25 Jun 2014 13:50:10 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 5417D2A53; Wed, 25 Jun 2014 13:50:07 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA03346; Wed, 25 Jun 2014 16:49:59 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1WznaJ-000DfD-2x; Wed, 25 Jun 2014 16:49:59 +0300 Message-ID: <53AAD356.20202@FreeBSD.org> Date: Wed, 25 Jun 2014 17:49:10 +0400 From: Andriy Gapon User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: attilio@FreeBSD.org, =?UTF-8?B?Um9nZXIgUGF1IE1vbm7DqQ==?= Subject: Re: svn commit: r267858 - in head/sys/dev: virtio/balloon xen/balloon References: <201406250951.s5P9p8YR017159@svn.freebsd.org> <53AACEAB.3090702@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Alan Cox , "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , "src-committers@freebsd.org" X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jun 2014 13:50:10 -0000 On 25/06/2014 17:44, Attilio Rao wrote: > Why? If VM needs more wired memory I assume that we can tune up the > default value of max_wired? > > I think that however your case makes an interesting point: if we want > to make unmanaged pages as inherently wired, we likely need a little > bit higher max_wired value. When I completed a patch for this, pho@ > couldn't reproduce any similar issue even with stress-testing (and > also, the places to allocate unmanaged pages and not requesting > VM_ALLOC_WIRED were very little, almost 0, with the exception of > vm_page_alloc_contig() calls) but I think it is a valid proposition. > > However I would still like to have more control on kernel-specific > wired memory for processes. I'm for example thinking to ARC vs. buffer > cache, where I expect the wired memory consumption to be much bigger > for the former case. My humble opinion is that userland page wiring should be tuned via resource limits and that vm.max_wired could be retired altogether. Kernel wiring ignores the knob anyway. -- Andriy Gapon