Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 4 Dec 2002 22:11:02 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 4 Dec 2002 22:11:01 -0500 Received: from TYO202.gate.nec.co.jp ([202.32.8.202]:16260 "EHLO TYO202.gate.nec.co.jp") by vger.kernel.org with ESMTP id ; Wed, 4 Dec 2002 22:11:01 -0500 To: David Gibson Cc: James Bottomley , "Adam J. Richter" , linux-kernel@vger.kernel.org Subject: Re: [RFC] generic device DMA implementation References: <20021205004744.GB2741@zax.zax> <200212050144.gB51iH105366@localhost.localdomain> <20021205023847.GA1500@zax.zax> Reply-To: Miles Bader System-Type: i686-pc-linux-gnu Blat: Foop From: Miles Bader Date: 05 Dec 2002 12:17:55 +0900 In-Reply-To: <20021205023847.GA1500@zax.zax> 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: 1017 Lines: 19 David Gibson writes: > It seems the "try to get consistent memory, but otherwise give me > inconsistent" is only useful on machines which: > (1) Are not fully consisent, BUT > (2) Can get consistent memory without disabling the cache, BUT > (3) Not very much of it, so you might run out. > > The point is, there has to be an advantage to using consistent memory > if it is available AND the possibility of it not being available. ... > Are there actually any machines with the properties described above? As I mentioned in my previous message, one of my platforms is like that -- PCI consistent memory must be allocated from a special pool of memory, which is only 2 megabytes in size. -Miles -- `Life is a boundless sea of bitterness' - 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/