From owner-freebsd-hackers Wed Mar 17 10:21:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id CA5C914C84 for ; Wed, 17 Mar 1999 10:21:14 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id DAA28404; Thu, 18 Mar 1999 03:20:50 +0900 (JST) Message-ID: <36EFEAE7.5028D72F@newsguy.com> Date: Thu, 18 Mar 1999 02:48:23 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: "Mark J. Taylor" , Sheldon Hearn , hackers@FreeBSD.org Subject: Re: Proposal: Define MAXMEM in GENERIC References: <12196.921649234@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > 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. The speculative memory probe flags is still a good idea. And the default should be the VM86 stuff (if it is compiled in). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "What happened?" "It moved, sir!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message