From: Jason Baietto <jason.baietto@ccur.com>
To: linux-kernel@vger.kernel.org
Subject: [RFC] Multiprocessor Control Interfaces
Date: 10 Dec 2001 15:14:47 -0500 [thread overview]
Message-ID: <1008015291.15138.0.camel@soybean> (raw)
Hello All,
I'm currently working on adding multiprocessor control interfaces
to Linux. My current efforts can be found here:
http://www.ccur.com/realtime/oss
These are clean-room implementations of similar tools that have
been available in our proprietary *nix for quite some time, and
so the interfaces have a fair amount of mileage under their belts.
Note that the scope is somewhat wider than just MP.
There has been some discussion of "chaff" and other interfaces
recently on this list, so in an effort to hopefully move towards
a standard more quickly I've gotten permission from my employer
to GPL the code I've written. I'm very interested in comments
and feedback on any or all of this work.
Here's the README file from the package:
This package contains:
run(1)
A multiprocessor control command line tool.
mpadvise(3)
A multiprocessor control library interface.
These services rely upon Robert Love's CPU Affinity patch
(version 2.4.16-1 was used for testing) which is available here:
http://www.kernel.org/pub/linux/kernel/people/rml/cpu-affinity/v2.4/
To build the code, simply unpack it and type "make". The code has
been tested on Red Hat 7.1 and 7.2 systems, though it is still
fairly new and almost certainly contains bugs.
An attempt was made to abstract the "cpuset" representation of
the current system in order to have binaries that in theory
could work on systems with more than 32 cpus. For this to work,
the run(1) command would need to be linked against a shared
mpadvise(3) library (currently only a static library is made).
This code is being released in the hopes that it will become
the basis for the Linux multiprocessor control standard interfaces.
I am very interested in getting feedback on this package,
so please contact me via email or LKML if you have any.
This source code is licensed under the GNU GPL Version 2.
Copyright (C) 2001 Concurrent Computer Corporation
--
Jason Baietto
jason.baiett@ccur.com
http://www.ccur.com/realtime/oss
next reply other threads:[~2001-12-10 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 20:14 Jason Baietto [this message]
2001-12-11 6:29 ` [RFC] Multiprocessor Control Interfaces Robert Love
2001-12-11 16:18 ` Jason Baietto
-- strict thread matches above, loose matches on Subject: below --
2001-12-11 1:59 Jason Baietto
2001-12-11 1:38 ` Tim Hockin
2001-12-11 16:31 ` Jason Baietto
2001-12-11 18:16 ` Tim Hockin
2001-12-12 15:11 ` Jason Baietto
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=1008015291.15138.0.camel@soybean \
--to=jason.baietto@ccur.com \
--cc=linux-kernel@vger.kernel.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