Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759586AbZD0UNK (ORCPT ); Mon, 27 Apr 2009 16:13:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750923AbZD0UMz (ORCPT ); Mon, 27 Apr 2009 16:12:55 -0400 Received: from ovro.ovro.caltech.edu ([192.100.16.2]:46040 "EHLO ovro.ovro.caltech.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750835AbZD0UMz (ORCPT ); Mon, 27 Apr 2009 16:12:55 -0400 Message-ID: <49F611C4.2030704@ovro.caltech.edu> Date: Mon, 27 Apr 2009 13:12:52 -0700 From: David Hawkins User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Kumar Gala CC: Ira Snyder , Liu Dave-R63238 , linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, Dan Williams , Timur Tabi Subject: Re: [PATCH] fsldma: use PCI Read Multiple command References: <20090424183517.GB23140@ovro.caltech.edu> <49F608B7.9080409@ovro.caltech.edu> <49F60A3A.4060402@freescale.com> <49F60BF8.8040404@ovro.caltech.edu> <46B638E2-885C-4281-81EA-CB685264E143@kernel.crashing.org> <49F60EC9.2050501@ovro.caltech.edu> <9B86B565-1A28-46CD-8C30-DECB3EBF0763@kernel.crashing.org> In-Reply-To: <9B86B565-1A28-46CD-8C30-DECB3EBF0763@kernel.crashing.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.0 (ovro.ovro.caltech.edu); Mon, 27 Apr 2009 13:12:55 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1589 Lines: 41 >>>> Can you give me an example of non-PCI memory that would be >>>> non-prefetchable that you'd like us to try? We can see if our >>>> host CPUs have an area like that ... we just need to know >>>> what device to look for first :) >>> You can mark the pci inbound window on the 83xx as non-prefetchable >>> (assuming 83xx is host). On a x86 host I doubt there is any easy way >>> to get non-prefetchable memory. >> >> Yep, we were going to do that, but chose to use the >> 1MB region already setup for the IMMRs since its already >> marked as non-prefetchable. We were only doing reads, so >> it wasn't going to hurt anything. >> >> I doubt that marking one of the other BAR regions >> as non-prefetchable will give a different result. >> However, we're more than happy to double-check if >> you'd like. > > Its possible you'll get a different result since IMMR is a register > space internal and thats normally a completely different bus than memory > would be (internal to the 83xx). I'd suggest double-checking w/a BAR > marked non-prefetch pointing to real memory. We had a 4k BAR1 setup to point to DDR memory. With prefetchable set, a 36-byte transfer generated a burst-of-8 32-bit words followed by a single transaction. With non-prefetchable set, the transfers were all single. So it works like we'd expect. Cheers, Dave -- 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/