From: bill4carson@gmail.com (bill4carson)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM hugetlb support?
Date: Tue, 21 Aug 2012 09:55:17 +0800 [thread overview]
Message-ID: <5032EA85.9030404@gmail.com> (raw)
In-Reply-To: <CANOLnOPLLQ=Cy5rvf5J7R96whrvLKO4HW9nVn4rQXqXCTVgCPA@mail.gmail.com>
On 2012?08?20? 07:18, Grazvydas Ignotas wrote:
> Hello,
>
> We are developing an application that's drawing various geometry on
> 1024x1024 framebuffer (lines, triangles, etc) and is running on
> Cortex-A8 CPU. It seems this kind of application is suffering badly
> from TLB misses, as A8 only has 32 entry TLB cache.
>
> I've found that hugetlb support patches have been posted some months
> ago [1]. I've been testing them with very good results [2]. Are there
> still plans to further develop them and eventually merge them?
>
Hi, Grazvydas
I'm glad you got performance boost with my hugetlb patch!
It's a pity this patch series probably will not be developed.
I really don't have much time to continue with the development,
especially provide statistics how arm huge tlb could be tunned
well to produce better performance, that's based on much testing
and also application specific.
Anyway, query and discussion are always welcome.
>
> [1] http://marc.info/?l=linux-arm-kernel&m=132912620601308&w=2
> [2] Cycle measurements of rendering full scene (using cycle counter in
> A8), x1000 cycles:
>
> normal hugetlb improvement
> scene1 28507 21351 34%
> scene2 11710 10138 16%
> scene3 17178 13631 26%
> scene4 4372 3810 15%
> scene5 3525 3255 8%
>
--
Love each day!
--bill
next prev parent reply other threads:[~2012-08-21 1:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 23:18 ARM hugetlb support? Grazvydas Ignotas
2012-08-21 1:55 ` bill4carson [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-20 8:27 Steve Capper
2012-08-21 9:57 ` Grazvydas Ignotas
2012-08-23 13:51 ` Steve Capper
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=5032EA85.9030404@gmail.com \
--to=bill4carson@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).