From owner-freebsd-hackers@freebsd.org  Thu Dec 29 14:45:25 2016
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53B26C961A8
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Thu, 29 Dec 2016 14:45:25 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 300FF19B7
 for <freebsd-hackers@freebsd.org>; Thu, 29 Dec 2016 14:45:24 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43])
 by mailout.nyi.internal (Postfix) with ESMTP id D781B20842
 for <freebsd-hackers@freebsd.org>; Thu, 29 Dec 2016 09:45:23 -0500 (EST)
Received: from web3 ([10.202.2.213])
 by compute3.internal (MEProxy); Thu, 29 Dec 2016 09:45:23 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=content-transfer-encoding:content-type
 :date:from:message-id:mime-version:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc; s=smtpout; bh=yoBMFPKPhrppFLpk0jsmhWSfp
 aU=; b=JBzkOD1dSJ6s0A38NeWf6Z7l1e36VEbzmlrVVbFsHhPG3BcLZdTpKibM8
 S0chvdcblcHe/jdNER88cR804je4CTrc8x3APtZPZME+PiSY82IgWncRjOk92kNt
 0MTrEZX20y8Qxn5pvzGlSoZepjIL5iqFuwA8QY9YVEc7XyTgxc=
X-ME-Sender: <xms:gyFlWD0GMN6r02qqvRO0SOBfFL-Ix72gi0B62tjQsYF6UcwumHKXlw>
Received: by mailuser.nyi.internal (Postfix, from userid 99)
 id AE1F19EE25; Thu, 29 Dec 2016 09:45:23 -0500 (EST)
Message-Id: <1483022723.3853404.832175825.1897001A@webmail.messagingengine.com>
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-hackers@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-9c115fcf
Date: Thu, 29 Dec 2016 08:45:23 -0600
Subject: vm.kmem_size_scale tunable only accepts whole numbers?
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Dec 2016 14:45:25 -0000

Hello,

Is there a reason why vm.kmem_size_scale only accepts whole numbers?
FreeNAS sets vm.kmem_size to 1.25*hw.realmem, but a smarter way of
setting this would to be able to use vm.kmem_size_scale with rational
numbers.

Thanks!

-- 
  Mark Felder
  ports-secteam member
  feld@FreeBSD.org