From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: <linuxppc-dev@ozlabs.org>, <cbe-oss-dev@ozlabs.org>
Cc: Arnd Bergmann <arnd.bergmann@de.ibm.com>
Subject: [PATCH 0/5] Support 64K pages mapping of SPE local stores on 4K kernel
Date: Tue, 20 Feb 2007 18:44:12 +1100 [thread overview]
Message-ID: <1171957452.861958.803775545202.qpush@grosgo> (raw)
This serie of patches supports userland mappings of SPE local stores
using 64K hardware pages rather than 4K on a kernel using 4K pages to
improve performances.
The current version of this serie relies on a hack to the generic code
which is probably not acceptable upsteam. I have plans to do a proper
fix but haven't had time to do it yet.
The first patch of the serie is fairly independant of the rest and
should be applied to 2.6.21 as I beleive it fixes a bug with handling
of huge pages from SPEs.
next reply other threads:[~2007-02-20 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 7:44 Benjamin Herrenschmidt [this message]
2007-02-20 7:44 ` [PATCH 2/5] This is a hack to get_unmapped_area to make the SPE 64K code work Benjamin Herrenschmidt
2007-02-20 7:44 ` [PATCH 1/5] powerpc: Fix spu SLB invalidations Benjamin Herrenschmidt
2007-02-20 7:44 ` [PATCH 3/5] powerpc: Introduce address space "slices" Benjamin Herrenschmidt
2007-03-01 6:11 ` [PATCH] Allow spufs to build as a module with slices enabled Michael Ellerman
2007-03-02 2:15 ` [Cbe-oss-dev] " Christoph Hellwig
2007-03-02 4:10 ` Michael Ellerman
2007-02-20 7:44 ` [PATCH 4/5] powerpc: Add ability to 4K kernel to hash in 64K pages Benjamin Herrenschmidt
2007-02-20 7:44 ` [PATCH 5/5] powerpc: spufs support for 64K LS mappings on 4K kernels Benjamin Herrenschmidt
2007-03-01 7:29 ` [PATCH 0/5] Support 64K pages mapping of SPE local stores on 4K kernel Michael Ellerman
-- strict thread matches above, loose matches on Subject: below --
2007-03-02 11:32 Benjamin Herrenschmidt
2007-04-21 20:33 ` Arnd Bergmann
2007-04-21 22:44 ` 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=1171957452.861958.803775545202.qpush@grosgo \
--to=benh@kernel.crashing.org \
--cc=arnd.bergmann@de.ibm.com \
--cc=cbe-oss-dev@ozlabs.org \
--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