Date: Thu, 18 Mar 1999 02:48:23 +0900 From: "Daniel C. Sobral" <dcs@newsguy.com> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: "Mark J. Taylor" <mtaylor@cybernet.com>, Sheldon Hearn <sheldonh@iafrica.com>, hackers@FreeBSD.org Subject: Re: Proposal: Define MAXMEM in GENERIC Message-ID: <36EFEAE7.5028D72F@newsguy.com> References: <12196.921649234@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?36EFEAE7.5028D72F>