Re: Unable to continue testing of 2.6.25

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Arjan van de Ven <arjan@...>
Cc: Andi Kleen <andi@...>, Frans Pop <elendil@...>, <linux-kernel@...>, Linus Torvalds <torvalds@...>
Date: Monday, February 18, 2008 - 3:18 pm

> > AFAIK mapping PCI memory WB is not allowed, so WC is really our only
 > > choice.

 > afaik that depends on the BAR being prefetchable or not.

In my case the BAR is prefetchable.

 > (and by your argument, ioremap_cached() would not be useful, and since that was, until
 > 2.6.25-rc1, the default behavior for ioremap(), would have caused massive problems)

I'm not sure what ioremap_cached() would really do in my case, since
the MTRRs for PCI memory are set to UC, so without monkeying with MTRR
contents (which can't really be done safely) the only choices we have
are leaving the mapping as UC or using PAT to get WC.

Also in my case I'm more concerned about latency of finishing a small
write rather than througput.  So I'm not sure that I would really want
to do a write to a WB mapping followed by CLFLUSH anyway.

 - R.
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Unable to continue testing of 2.6.25, Frans Pop, (Sun Feb 17, 5:25 am)
Re: Unable to continue testing of 2.6.25, Arjan van de Ven, (Sun Feb 17, 4:46 pm)
Re: Unable to continue testing of 2.6.25, Andi Kleen, (Mon Feb 18, 8:31 am)
Re: Unable to continue testing of 2.6.25, Arjan van de Ven, (Mon Feb 18, 12:50 pm)
Re: Unable to continue testing of 2.6.25, Andi Kleen, (Mon Feb 18, 1:11 pm)
Re: Unable to continue testing of 2.6.25, Arjan van de Ven, (Mon Feb 18, 1:32 pm)
Re: Unable to continue testing of 2.6.25, Roland Dreier, (Mon Feb 18, 2:53 pm)
Re: Unable to continue testing of 2.6.25, Arjan van de Ven, (Mon Feb 18, 3:07 pm)
Re: Unable to continue testing of 2.6.25, Roland Dreier, (Mon Feb 18, 3:18 pm)
Re: Unable to continue testing of 2.6.25, Siddha, Suresh B, (Tue Feb 19, 3:42 pm)
Re: Unable to continue testing of 2.6.25, Alan Cox, (Mon Feb 18, 2:40 pm)
Re: Unable to continue testing of 2.6.25, Arjan van de Ven, (Mon Feb 18, 2:52 pm)
Re: Unable to continue testing of 2.6.25, Alan Cox, (Mon Feb 18, 4:15 pm)
Re: Unable to continue testing of 2.6.25, Andi Kleen, (Mon Feb 18, 2:52 pm)
Re: Unable to continue testing of 2.6.25, Ingo Molnar, (Mon Feb 18, 3:18 pm)
Re: Unable to continue testing of 2.6.25, Andi Kleen, (Tue Feb 19, 5:35 am)
Re: Unable to continue testing of 2.6.25, Arjan van de Ven, (Mon Feb 18, 2:32 pm)
Re: Unable to continue testing of 2.6.25, Adrian Bunk, (Sun Feb 17, 9:16 am)
Re: Unable to continue testing of 2.6.25, Frans Pop, (Tue Feb 19, 5:55 pm)
Re: Unable to continue testing of 2.6.25, Adrian Bunk, (Tue Feb 19, 6:19 pm)
Re: Unable to continue testing of 2.6.25, Frans Pop, (Tue Feb 19, 6:49 pm)
Re: Unable to continue testing of 2.6.25, Harvey Harrison, (Tue Feb 19, 6:15 pm)
Re: Unable to continue testing of 2.6.25, Arjan van de Ven, (Tue Feb 19, 5:59 pm)
Re: Unable to continue testing of 2.6.25, Tilman Schmidt, (Sun Feb 17, 3:24 pm)
Re: Unable to continue testing of 2.6.25, David Miller, (Sun Feb 17, 10:33 pm)
Re: Unable to continue testing of 2.6.25, Andi Kleen, (Mon Feb 18, 8:27 am)
Re: Unable to continue testing of 2.6.25, Tilman Schmidt, (Mon Feb 18, 7:40 am)
Re: Unable to continue testing of 2.6.25, Adrian Bunk, (Sun Feb 17, 3:44 pm)
Re: Unable to continue testing of 2.6.25, Paul Jackson, (Sun Feb 17, 4:38 pm)
Re: Unable to continue testing of 2.6.25, Arjan van de Ven, (Sun Feb 17, 4:51 pm)
Re: Unable to continue testing of 2.6.25, Frans Pop, (Tue Feb 19, 6:41 pm)