Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261907AbTIPObe (ORCPT ); Tue, 16 Sep 2003 10:31:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261909AbTIPObe (ORCPT ); Tue, 16 Sep 2003 10:31:34 -0400 Received: from mikonos.cyclades.com.br ([200.230.227.67]:43538 "EHLO firewall.cyclades.com.br") by vger.kernel.org with ESMTP id S261907AbTIPObb (ORCPT ); Tue, 16 Sep 2003 10:31:31 -0400 Date: Tue, 16 Sep 2003 11:33:27 -0300 (BRT) From: Marcelo Tosatti X-X-Sender: marcelo@logos.cnet To: Stephan von Krawczynski cc: Marcelo Tosatti , , Subject: Re: experiences beyond 4 GB RAM with 2.4.22 In-Reply-To: <20030916153658.3081af6c.skraw@ithnet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1112 Lines: 30 On Tue, 16 Sep 2003, Stephan von Krawczynski wrote: > On Tue, 16 Sep 2003 10:11:49 -0300 (BRT) > Marcelo Tosatti wrote: > > > Oh... Jens just pointed bounce buffering is needed for the upper 2Gs. > > > > Maybe you have a SCSI card+disks to test ? 8) > > Well, I do understand the bounce buffer problem, but honestly the current way > of handling the situation seems questionable at least. If you ever tried such a > system you notice it is a lot worse than just dumping the additional ram above > 4GB. You can really watch your network connections go bogus which is just > unacceptable. All is fine with 4GB? > Is there any thinkable way to ommit the bounce buffers and still > do something useful with the beyond-4GB ram parts? > We should not leave the current bad situation as is... No way to omit the bounce buffers. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/