Message-ID: <47F11616.3020403@linux.intel.com>
Date: Mon, 31 Mar 2008 09:49:26 -0700
From: Arjan van de Ven <arjan@linux.intel.com>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Thomas_Hellstr=F6m?= <thomas@tungstengraphics.com>
CC: Andi Kleen <andi@firstfloor.org>, Dave Airlie <airlied@redhat.com>,
       linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com
Subject: Re: [PATCH] x86: create array based interface to change page attribute
References: <1206940788.7250.13.camel@clockmaker.usersys.redhat.com> <87myof8ief.fsf@basil.nowhere.org> <47F098E8.1050605@tungstengraphics.com> <20080331083816.GC29105@one.firstfloor.org> <47F0A988.7010707@tungstengraphics.com> <20080331091829.GD29105@one.firstfloor.org> <47F0C6C2.2000004@tungstengraphics.com> <47F10C62.7040500@linux.intel.com> <47F11443.7050302@tungstengraphics.com>
In-Reply-To: <47F11443.7050302@tungstengraphics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1749
Lines: 46

Thomas Hellstr?m wrote:
> Arjan van de Ven wrote:
>> Thomas Hellstr?m wrote:
>>
>>> Let me rehprase. Not really time-critical but it is of some 
>>> importance that CPA is done quickly.
>>> We're dealing with the tradeoff of reading from uncached device memory 
>>
>> uncached or write combining ?
> The user-space mappings (the ones that we really use) are usually 
> write-combined, whereas the kernel mappings are uncached. (I think this 
> is OK since both mapping types implies no cache coherency). 

This is not officially allowed and may tripple fault your cpu..
To comply with the spec one needs to have ALL mappings the same unfortunately.
(And yes, this is a hard problem)

>Even if 
> (IIRC) write combining is theoretically prefetchable, some devices give 
> read speeds around 9MB/s.
>>
>>> vs taking the pages out of
>>> AGP, setting up a cache-coherent mapping, read and then change back. 
>>> What we'd really would like to set up is a pool of completely 
>>> unmapped (like highmem) pages. Then we could, to a large extent, 
>>> avoid the CPA calls.
>>
>> changing attributes by nature means a tlb flush and a bunch of 
>> expensive cache work.
>> That's never going to be cheap, I guess it all depends on how much 
>> work you do
>> on the memory for it to pay off or not...
> Indeed. Actually with the new non-wbinvd() CPA, We seem to benefit 
> already if the buffer is a single page, though it's probably hard to 
> measure the impact of repopulating the tlb.
> 
> /Thomas
> 
> 
> 

--
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/