All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Stephen Williams <steve@icarus.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: How to map memory uncached on PPC.
Date: Sat, 20 Aug 2005 14:08:28 -0400	[thread overview]
Message-ID: <20050820180825.GG2736@tuxdriver.com> (raw)
In-Reply-To: <4307536E.4070800@icarus.com>

On Sat, Aug 20, 2005 at 08:59:42AM -0700, Stephen Williams wrote:
> Benjamin Herrenschmidt wrote:

> >A simple experiment you can do is limit the memory used by the kernel
> >(booting with mem=xxxx) and then use mmap of /dev/mem to map the
> >remaining memory like if it was an IO device, uncached. With that, you
> >get a quick hack solution to validate the performance benefit at least.
> 
> I did an even simpler experiment: I commented out the pci_map_single,
> which on a PPC only has the effect of calling invalidate_dcache_range
> and returning the virt_to_bus of the address. Obviously, the cache
> is still enabled for the processor, and the image data may get
> corrupted, but this was a performance test, not a solution.

If your purpose is to evaluate performance, doesn't having the cache
enabled limit the usefulness of your test?  For example if your cache
uses a write-back policy then your test will probably outperform the
actual uncached accesses.  YMMV, I suppose...

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2005-08-20 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 15:17 How to map memory uncached on PPC Stephen Williams
2005-08-20  1:06 ` Benjamin Herrenschmidt
2005-08-20 15:59   ` Stephen Williams
2005-08-20 18:08     ` John W. Linville [this message]
2005-08-21 15:06       ` Stephen Williams
  -- strict thread matches above, loose matches on Subject: below --
2005-08-19 16:18 Stephen Williams

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=20050820180825.GG2736@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=steve@icarus.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.