From owner-freebsd-hackers Tue Mar 16 21:40:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id D422A14EC0 for ; Tue, 16 Mar 1999 21:40:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA12198; Tue, 16 Mar 1999 21:40:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Mark J. Taylor" Cc: Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-reply-to: Your message of "Sun, 14 Mar 1999 13:19:05 EST." Date: Tue, 16 Mar 1999 21:40:34 -0800 Message-ID: <12196.921649234@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For our NetMAX product (shameless plug: http://www.netmax.com/), > which is 2.2.7+ based (we're working on a 3.1 version), we've > added two additional boot options: > 1) -M always perform speculative memory probe > 2) -m never perform speculative memory probe Now there's an idea, though I'd go a little further: Why not add a new variable to the 3-stage loader so you could simply say: boot> set maxmem=64M boot> load /kernel boot> boot (etc) To set the memory size to some exact value (which you might know better than the probe). This strikes me as far more general and easy to understand as well. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message