From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Arnd Bergmann <arnd@arndb•de>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [RFC/PATCH] powerpc: introduce "slices" (aka. meta-segments)
Date: Fri, 16 Feb 2007 07:49:49 +1100 [thread overview]
Message-ID: <1171572589.5644.23.camel@localhost.localdomain> (raw)
In-Reply-To: <200702152009.58367.arnd@arndb.de>
On Thu, 2007-02-15 at 20:09 +0100, Arnd Bergmann wrote:
> On Thursday 15 February 2007 09:36, Benjamin Herrenschmidt wrote:
> > arch/powerpc/Kconfig | 5
> > arch/powerpc/kernel/asm-offsets.c | 16 -
> > arch/powerpc/mm/Makefile | 1
> > arch/powerpc/mm/hash_utils_64.c | 4
> > arch/powerpc/mm/hugetlbpage.c | 514 -------------------------------------
> > arch/powerpc/mm/mmu_context_64.c | 4
> > arch/powerpc/mm/slb.c | 11
> > arch/powerpc/mm/slb_low.S | 50 ++-
> > arch/powerpc/mm/slice.c | 517 ++++++++++++++++++++++++++++++++++++++
> > include/asm-powerpc/mmu.h | 12
> > include/asm-powerpc/paca.h | 2
> > include/asm-powerpc/page_64.h | 83 ++----
> > 12 files changed, 625 insertions(+), 594 deletions(-)
>
> I tried to review your patch, but I found it hard because of the amount of
> code that that just gets moved from hugetlbpage.c to slice.c. Could you
> send the next version of as two patches, with one of them only moving the
> code without changing it?
There is not that much code that gets moved. It mostly gets rewritten.
Ben.
prev parent reply other threads:[~2007-02-15 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 8:36 [RFC/PATCH] powerpc: introduce "slices" (aka. meta-segments) Benjamin Herrenschmidt
2007-02-15 19:09 ` Arnd Bergmann
2007-02-15 20:49 ` Benjamin Herrenschmidt [this message]
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=1171572589.5644.23.camel@localhost.localdomain \
--to=benh@kernel$(echo .)crashing.org \
--cc=arnd@arndb$(echo .)de \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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