From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linuxppc64-dev@ozlabs.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/7] spufs: The SPU file system
Date: Mon, 29 Aug 2005 11:09:49 -0700 [thread overview]
Message-ID: <43134F6D.1080602@am.sony.com> (raw)
In-Reply-To: <200508281844.18187.arnd@arndb.de>
Arnd Bergmann wrote:
> On Freedag 26 August 2005 10:17, Pekka Enberg wrote:
>
>>I am confused. The code is architecture specific and does device I/O. Why do
>>you want to put this in fs/ and not drivers/?
>
>
> I never really thought of it as a device driver but rather an architecture
> extension, so it started out in arch/ppc64/kernel. Since most of the code
> is interacting with VFS, it is now in fs/spufs. I don't really care about
> the location, but I among the possible places to put the code (with the
> unified arch/powerpc tree), I'd suggest (best first)
>
> 1) arch/powerpc/platforms/cell
> 2) arch/powerpc/spe
> 3) fs/spufs
> 4) drivers/spe
>
> 1) would be the place where I want to have the low-level code
> (currently arch/ppc64/kernel/spu_base.c) anyway, so it makes
> sense to have everything in there that I maintain.
> 2) might work better if we at a later point have multiple platform
> types in arch/powerpc that use SPEs, e.g if we want to keep
> Playstation code separate from generic Cell.
>
I think putting it in 'arch/powerpc/platforms/cell' is fine for now. We'll
be better able to judge if we need to and how to split off platform specifics
when we have code for more cell platforms.
-Geoff
prev parent reply other threads:[~2005-08-29 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 22:03 [PATCH 1/7] spufs: The SPU file system Arnd Bergmann
2005-08-26 8:17 ` Pekka Enberg
2005-08-28 16:44 ` Arnd Bergmann
2005-08-28 20:05 ` Pekka Enberg
2005-08-29 18:09 ` Geoff Levand [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=43134F6D.1080602@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=penberg@cs.helsinki.fi \
/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.