public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc64-dev@ozlabs.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/7] spufs: The SPU file system
Date: Sun, 28 Aug 2005 23:05:27 +0300	[thread overview]
Message-ID: <1125259528.3007.4.camel@localhost> (raw)
In-Reply-To: <200508281844.18187.arnd@arndb.de>

On Sun, 2005-08-28 at 18:44 +0200, Arnd Bergmann wrote:
> 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.

I am happy with 1, 2, and 4. You could, of course, abstract away the
general purpose parts of spufs (for example, if we had other similar
architecture extensions that could share the code) and put them in 3 but
that would probably just introduce unnecessary complexity.

			Pekka


  reply	other threads:[~2005-08-28 20:06 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 [this message]
2005-08-29 18:09     ` Geoff Levand

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=1125259528.3007.4.camel@localhost \
    --to=penberg@cs.helsinki.fi \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-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