From owner-freebsd-hackers Mon Apr 20 00:15:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22252 for freebsd-hackers-outgoing; Mon, 20 Apr 1998 00:15:21 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22245 for ; Mon, 20 Apr 1998 07:15:16 GMT (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA00372; Mon, 20 Apr 1998 02:14:42 -0500 (EST) (envelope-from toor) Message-Id: <199804200714.CAA00372@dyson.iquest.net> Subject: Re: 1 Gbyte of ram In-Reply-To: from Andrzej Bialecki at "Apr 20, 98 08:22:42 am" To: abial@nask.pl (Andrzej Bialecki) Date: Mon, 20 Apr 1998 02:14:42 -0500 (EST) Cc: dg@root.com, rzig@verio.net, dec@phoenix.its.rpi.edu, hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki said: > > BTW. I don't quite understand what's the problem with bounce buffers - can > they be made to work out-of-the-box with large RAMs or can't they??? As it > is now (and has been for some time), the boot.flp dies on machines with >= > 512MB RAM, and IMHO this shouldn't happen... > The bounce buffer problems are simply initialization issues. If other kernel data structures are too big, the bounce buffers are put too far up in the physical address space, and the bounce memory allocated is too big. It shouldn't happen, and should not be a problem in -current any more. We'll have a new "bounce" scheme soon, so that stuff is legacy anyway. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message