From owner-freebsd-hackers Sun Mar 14 19: 1:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dingo.cdrom.com (castles125.castles.com [208.214.165.125]) by hub.freebsd.org (Postfix) with ESMTP id 392C914DF6 for ; Sun, 14 Mar 1999 19:01:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA09228; Sun, 14 Mar 1999 18:55:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903150255.SAA09228@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki Cc: Mike Smith , Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: Proposal: Define MAXMEM in GENERIC In-reply-to: Your message of "Mon, 15 Mar 1999 02:14:44 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Mar 1999 18:55:08 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 14 Mar 1999, Mike Smith wrote: > > > We'd probably be better off using VM86 and the BIOS memory probe code, > > which will give us the best of both worlds. > > > > The code's been in the system for a long time now, and completely > > obsoletes the (bogus from day 1) speculative probe. > > I wonder if it's possible to add a MAXMEM environment variable in > bootloader... then those who know better could set it to the real value. You'd do this the same way the other tunables were done. I've actually been talking to David Filo about tunables, and I think I have a better model for them in the works. It should make it possible to just about completely eliminate param.c (some statically-sized items may need to be fixed up). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message