All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Prylli <loic@myri.com>
To: Brice Goglin <brice@myri.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org,
	"venkatesh.pallipadi@intel.com" <venkatesh.pallipadi@intel.com>
Subject: Re: howto use ioremap_wc?
Date: Mon, 02 Jun 2008 14:18:04 -0400	[thread overview]
Message-ID: <4844395C.2010900@myri.com> (raw)
In-Reply-To: <48441F73.5040005@myri.com>

On 06/02/2008 12:27 PM, Brice Goglin wrote:
> Arjan van de Ven wrote:
>   
>> Ok this leads to a question: since write combining is effectively an
>> extension (eg relaxation) to uncached, how much do you care if you
>> actually get uncached? Eg can you just use the "WC" function even for
>> the case where you get an uncached mapping ?
>>   
>>     
>
> WC is strictly required for our "wcfifo" path,




To be more accurate about the above statement, that codepath will still 
work correctly even if the mapping ends-up being uncached, but that 
could lead to a 16X slowdown on some machines, since that path was 
really designed for the WC case.


Anyway that codepath does not really matter as Brice mentioned 
afterwards :-)



>  but this path is actually
> not so important nowadays. It is disabled by default and might even be
> removed in the future. So, no, myri10ge itself does not really need to
> know whether the mapping is actually WC.
>   




Loic


  reply	other threads:[~2008-06-02 18:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-31  9:02 howto use ioremap_wc? Brice Goglin
2008-06-01  1:54 ` Arjan van de Ven
2008-06-02 16:27   ` Brice Goglin
2008-06-02 18:18     ` Loic Prylli [this message]
2008-06-03  2:18     ` Arjan van de Ven
2008-06-05  4:53   ` Roland Dreier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4844395C.2010900@myri.com \
    --to=loic@myri.com \
    --cc=arjan@infradead.org \
    --cc=brice@myri.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=venkatesh.pallipadi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.