From: Arnd Bergmann <arnd@arndb.de>
To: akpm@osdl.org
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc64-dev@ozlabs.org, linux-kernel@vger.kernel.org,
mnutter@us.ibm.com
Subject: [PATCH 0/5] SPU file system for 2.6.15-rc-mm
Date: Tue, 15 Nov 2005 15:53:47 -0500 [thread overview]
Message-ID: <20051115205347.395355000@localhost> (raw)
I'd like to have the SPU file system included in the -mm kernel
to get broader review and eventually have it merged in 2.6.16.
This version now puts all the spufs files under
arch/powerpc/platforms/cell/spufs instead of fs/spufs, since it
is really specific to that platform.
The interface has now stabilized on a set of files per logical
SPU that can be accessed with read/write and sometime poll
or mmap but not ioctl as well as two new system calls, spu_run
and spu_create.
As discussed, the system call numbers that I am using here
conflict with those from the perfmon patches, so I'm moving
the perfmon syscall range to start at 280. This means that
the first patch gets to be applied on top of
perfmon2-reserve-system-calls-reserve-spu-slots.patch.
Arnd <><
--
next reply other threads:[~2005-11-15 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 20:53 Arnd Bergmann [this message]
2005-11-15 20:53 ` [PATCH 2/5] spufs: switchable spu contexts Arnd Bergmann
2005-11-15 20:53 ` [PATCH 3/5] kernel-side context switch code for spufs Arnd Bergmann
2005-11-15 20:53 ` [PATCH 4/5] spufs: add spu-side context switch code Arnd Bergmann
2005-11-15 20:53 ` [PATCH 5/5] spufs: cooperative scheduler support Arnd Bergmann
[not found] ` <20051115210408.327453000@localhost>
2005-11-16 1:41 ` [PATCH 1/5] spufs: The SPU file system, base Andrew Morton
2005-11-16 14:26 ` [PATCH] spufs: Make all exports GPL-only Arnd Bergmann
2005-11-16 5:15 ` [PATCH 1/5] spufs: The SPU file system, base Paul Mackerras
2005-11-16 5:26 ` Andrew Morton
2005-11-16 14:38 ` Arnd Bergmann
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=20051115205347.395355000@localhost \
--to=arnd@arndb.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=mnutter@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox