From: Jason Baietto <jason.baietto@ccur.com>
To: Tim Hockin <thockin@hockin.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Multiprocessor Control Interfaces
Date: 11 Dec 2001 11:31:47 -0500 [thread overview]
Message-ID: <1008088311.16656.4.camel@soybean> (raw)
In-Reply-To: <200112110138.fBB1cqS09363@www.hockin.org>
In-Reply-To: <200112110138.fBB1cqS09363@www.hockin.org>
On Mon, 2001-12-10 at 20:38, Tim Hockin wrote:
>
> http://www.hockin.org/~thockin/pset. Not finished, but could be.
Yes, many similarities. I like the idea of having a single system
call that provides so much multiprocessor control and information.
If such a system call was ever standardized upon, I would gladly
support it in my "run" tool, though I fear that it would always be
functionally limited without /proc present.
next prev parent reply other threads:[~2001-12-11 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 1:59 [RFC] Multiprocessor Control Interfaces Jason Baietto
2001-12-11 1:38 ` Tim Hockin
2001-12-11 16:31 ` Jason Baietto [this message]
2001-12-11 18:16 ` Tim Hockin
2001-12-12 15:11 ` Jason Baietto
-- strict thread matches above, loose matches on Subject: below --
2001-12-10 20:14 Jason Baietto
2001-12-11 6:29 ` Robert Love
2001-12-11 16:18 ` 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=1008088311.16656.4.camel@soybean \
--to=jason.baietto@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thockin@hockin.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