From owner-freebsd-arch@FreeBSD.ORG Fri Feb 28 05:15:06 2014 Return-Path: Delivered-To: arch@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 102374A0 for ; Fri, 28 Feb 2014 05:15:06 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D965D1FF1 for ; Fri, 28 Feb 2014 05:15:05 +0000 (UTC) Received: from Julian-MBP3.local (ppp121-45-232-70.lns20.per1.internode.on.net [121.45.232.70]) (authenticated bits=0) by vps1.elischer.org (8.14.7/8.14.7) with ESMTP id s1S5EtMo062710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 27 Feb 2014 21:14:58 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <53101B49.2010400@freebsd.org> Date: Fri, 28 Feb 2014 13:14:49 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: arch@FreeBSD.org Subject: Re: small kernel kernel option... References: <20140226214816.GB92037@funkthat.com> In-Reply-To: <20140226214816.GB92037@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Feb 2014 05:15:06 -0000 On 2/27/14, 5:48 AM, John-Mark Gurney wrote: > I'm about to commit a change to sha256 to speed it up, but the cost > of that speed up is an increase in code/data size from just under 1k > to almost 9k (as measured on amd64)... this increase is from unrolling > a loop.. > > Maybe we should have a global kernel option, SMALL_KERNEL, or something > similar that can be used to shrink code size for those that are trying > to build small embedded devices... > > Or do we already have this option, but I just don't know about it? > > I know 8k isn't much, but, a billion here and a billion there and pretty > soon you're talking about real money.. :) > > Comments? > it's the same as the old "space vs time" optimisations in UFS. maybe "OPTIMIZE_FOR_SPACE" vs "OPTIMIZE_FOR_SPEED"