Date: Wed, 17 Mar 1999 09:41:09 -0700 From: Nate Williams <nate@mt.sri.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: <199903171641.JAA10150@mt.sri.com> In-Reply-To: <12196.921649234@zippy.cdrom.com> References: <Pine.BSF.4.01.9903141246550.17166-100000@gateway.cybernet.com> <12196.921649234@zippy.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. I would think a Forth hacker could do this, given that the flags to the npx device can be used to specify the amount of memory in the system. (Although, I could find it documented anywhere obvious when I went looking for it in the man pages.) /sys/i386/isa/npx.c: revision 1.32 date: 1996/11/11 20:39:03; author: bde; state: Exp; lines: +47 -13 ... Added a boot-time way to set the memory size (iosiz in config, iosize in userconfig for npx0). ... Nate 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?199903171641.JAA10150>