From: "James Buchanan" <jamesbuch@iprimus.com.au>
To: <linux-kernel@vger.kernel.org>
Subject: SMP-Linux
Date: Tue, 11 Feb 2003 02:36:48 +1100 [thread overview]
Message-ID: <001501c2d11a$3ad9c3a0$59951ad3@windows> (raw)
Hello List,
I am new to this so please forgive this post if it seems stupid.
Is it possible to design a SMP-Linux kernel with architecture
independent SMP support, for example, like the VFS provides an
interface to specific filesystems, the "VSMP" can provide an
architecture independent way to support SMP? There can be a function
that does the spinlock stuff and underneath is a machine dependent
implementation (this is already done for x86, what about other MP
capable architectures?), and same for the scheduler. Lots of other
stuff like TLB issues and so on would have to be taken care of as
well. I'm no expert on SMP so I don't really know if a "virtual" SMP
support is possible in the way I am describing it.
Is this an interesting idea to anyone? I expect it has been thought
of before, but maybe it needs a hell of a lot of research to even
begin thinking about it seriously. If anyone is interesting in really
thrashing this out off list (or on list, but is this considered bad
netiquette?), please mail me. I am very interested in discussing this
in horrid detail :-)
When I buy my SMP system, I plan to hack in the first stages of such
"VSMP" support if it's feasible.
Again, I don't really know what I'm doing so please go easy on me :-)
I am still in the early stages of soaking up the stuff in the Intel
CPU programming manuals.
Thanks!
James
next reply other threads:[~2003-02-10 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 15:36 James Buchanan [this message]
2003-02-10 16:08 ` SMP-Linux John W. M. Stevens
2003-02-10 16:16 ` SMP-Linux James Buchanan
2003-02-20 17:39 ` SMP-Linux Benjamin Herrenschmidt
[not found] ` <200302211645.07356.jamesbuch@iprimus.com.au>
2003-02-20 17:53 ` SMP-Linux Benjamin Herrenschmidt
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='001501c2d11a$3ad9c3a0$59951ad3@windows' \
--to=jamesbuch@iprimus.com.au \
--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