From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux powerpc <linuxppcleo@gmail.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc:Fix rheap alignment problem
Date: Sat, 01 Jul 2006 17:21:06 +1000 [thread overview]
Message-ID: <1151738466.27137.24.camel@localhost.localdomain> (raw)
In-Reply-To: <a0bc9bf80606302335p7ba227afwf69dc42e2eada64b@mail.gmail.com>
On Sat, 2006-07-01 at 14:35 +0800, Linux powerpc wrote:
> Yes, it was used for allocating dual port RAM for CPM. And now we are
> adding QE support to powerpc arch which need to use rheap(QE is next
> generation for CPM). Please see the patches I <leoli@freescale.com>
> just posted for 8360epb support. Moreover, previous CPM support is
> adding to powerpc arch too.
Ok, well, I don't have anything specifically against that code, I was
just wondering if it may not duplicate something we already have (yet
another space allocator basically)...
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linux powerpc <linuxppcleo@gmail.com>
Cc: Rune Torgersen <runet@innovsys.com>,
Li Yang-r58472 <LeoLi@freescale.com>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc:Fix rheap alignment problem
Date: Sat, 01 Jul 2006 17:21:06 +1000 [thread overview]
Message-ID: <1151738466.27137.24.camel@localhost.localdomain> (raw)
In-Reply-To: <a0bc9bf80606302335p7ba227afwf69dc42e2eada64b@mail.gmail.com>
On Sat, 2006-07-01 at 14:35 +0800, Linux powerpc wrote:
> Yes, it was used for allocating dual port RAM for CPM. And now we are
> adding QE support to powerpc arch which need to use rheap(QE is next
> generation for CPM). Please see the patches I <leoli@freescale.com>
> just posted for 8360epb support. Moreover, previous CPM support is
> adding to powerpc arch too.
Ok, well, I don't have anything specifically against that code, I was
just wondering if it may not duplicate something we already have (yet
another space allocator basically)...
Ben.
next prev parent reply other threads:[~2006-07-01 7:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 13:02 [PATCH] powerpc:Fix rheap alignment problem Li Yang-r58472
2006-06-30 23:13 ` Benjamin Herrenschmidt
2006-06-30 23:13 ` Benjamin Herrenschmidt
2006-07-01 4:13 ` Rune Torgersen
2006-07-01 6:35 ` Linux powerpc
2006-07-01 7:21 ` Benjamin Herrenschmidt [this message]
2006-07-01 7:21 ` Benjamin Herrenschmidt
2006-07-01 10:25 ` Christoph Hellwig
2006-07-01 10:25 ` Christoph Hellwig
2006-07-01 14:34 ` Kumar Gala
2006-07-01 14:34 ` Kumar Gala
2006-07-01 14:50 ` Pantelis Antoniou
2006-07-01 14:50 ` Pantelis Antoniou
2006-07-02 3:54 ` Rune Torgersen
2006-07-02 5:18 ` Pantelis Antoniou
2006-07-02 5:18 ` Pantelis Antoniou
2006-07-03 11:08 ` Benjamin Herrenschmidt
2006-07-03 11:08 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2006-07-03 6:49 Li Yang-r58472
2006-07-03 12:19 Li Yang-r58472
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=1151738466.27137.24.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppcleo@gmail.com \
--cc=paulus@samba.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 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.