From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ayman El-Khashab <ayman@elkhashab.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: ppc44x - how do i optimize driver for tlb hits
Date: Fri, 24 Sep 2010 08:01:04 +1000 [thread overview]
Message-ID: <1285279264.5158.18.camel@pasglop> (raw)
In-Reply-To: <20100923151246.GA17015@crust.elkhashab.com>
On Thu, 2010-09-23 at 10:12 -0500, Ayman El-Khashab wrote:
> I've implemented a working driver on my 460EX. it allocates a couple
> of buffers of 4MB each. I have a custom memcmp algorithm in asm that
> is extremely fast in user space, but 1/2 as fast when run on these
> buffers.
>
> my tests are showing that the algorithm seems to be memory bandwidth
> bound. my guess is that i am having tlb or cache misses (my algo
> uses the dbct) that is slowing performance. curiously when in user
> space, i can affect the performance by small changes in the size of
> the buffer, i.e. 4MB + 32B is fast, 4MB + 4K is much worse.
>
> Can i adjust my driver code that is using kmalloc to make sure that
> the ppc44x has 4MB tlb entries for these and that they stay put?
Anything you allocate with kmalloc() is going to be mapped by bolted
256M TLB entries, so there should be no TLB misses happening in the
kernel case.
Cheers,
Ben.
next prev parent reply other threads:[~2010-09-23 22:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 15:12 ppc44x - how do i optimize driver for tlb hits Ayman El-Khashab
2010-09-23 22:01 ` Benjamin Herrenschmidt [this message]
2010-09-23 22:35 ` Ayman El-Khashab
2010-09-24 1:07 ` Benjamin Herrenschmidt
2010-09-24 2:58 ` Ayman El-Khashab
2010-09-24 4:43 ` Benjamin Herrenschmidt
2010-09-24 10:30 ` Josh Boyer
2010-09-24 13:08 ` Ayman El-Khashab
2010-09-24 22:11 ` Benjamin Herrenschmidt
2010-10-03 19:13 ` Ayman El-Khashab
2010-10-03 22:38 ` Benjamin Herrenschmidt
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=1285279264.5158.18.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=ayman@elkhashab.com \
--cc=linuxppc-dev@ozlabs.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).