From: Rik van Riel <riel@conectiva.com.br>
To: "David L. Nicol" <david@kasey.umkc.edu>
Cc: Zack Brown <zbrown@tumblerings.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Will Mosix go into the standard kernel?
Date: Tue, 27 Feb 2001 18:32:44 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33.0102271829030.5502-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <3A9C1A3A.8BC1BCF2@kasey.umkc.edu>
On Tue, 27 Feb 2001, David L. Nicol wrote:
> I've thought that it would be good to break up the different
> clustering frills -- node identification, process migration,
> process hosting, distributed memory, yadda yadda blah, into
> separate bite-sized portions.
It would also be good to share parts of the infrastructure
between the different clustering architectures ...
> Is there a good list to discuss this on? Is this the list?
> Which pieces of clustering-scheme patches would be good to have?
I know each of the cluster projects have mailing lists, but
I've never heard of a list where the different projects come
together to eg. find out which parts of the infrastructure
they could share, or ...
Since I agree with you that we need such a place, I've just
created a mailing list:
linux-cluster@nl.linux.org
To subscribe to the list, send an email with the text
"subscribe linux-cluster" to:
majordomo@nl.linux.org
I hope that we'll be able to split out some infrastructure
stuff from the different cluster projects and we'll be able
to put cluster support into the kernel in such a way that
we won't have to make the choice which of the N+1 cluster
projects should make it into the kernel...
regards,
Rik
--
Linux MM bugzilla: http://linux-mm.org/bugzilla.shtml
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/
http://www.conectiva.com/ http://distro.conectiva.com/
next prev parent reply other threads:[~2001-02-27 21:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 17:17 Will Mosix go into the standard kernel? Zack Brown
2001-02-27 21:20 ` David L. Nicol
2001-02-27 21:32 ` Rik van Riel [this message]
2001-02-28 23:06 ` Daniel Ridge
2001-02-28 23:58 ` Albert D. Cahalan
2001-03-01 0:53 ` Dan Hollis
2001-03-01 1:35 ` Daniel Ridge
2001-03-01 2:37 ` zbrown
2001-03-02 0:52 ` Pavel Machek
2001-02-27 21:37 ` Alexander Viro
2001-02-27 21:56 ` Zack Brown
2001-02-27 22:29 ` zbrown
2001-02-27 22:33 ` J . A . Magallon
2001-02-28 17:59 ` Ric Wheeler
2001-02-27 17:31 Christopher Chimelis
2001-02-27 17:40 ` Zack Brown
[not found] <fa.o4k0c0v.smgv2v@ifi.uio.no>
[not found] ` <fa.m9jgfcv.17n8s2n@ifi.uio.no>
2001-03-01 15:02 ` Tor Arntsen
2001-03-01 19:13 ` Tim Wright
2001-03-02 10:22 Tor Arntsen
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=Pine.LNX.4.33.0102271829030.5502-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=david@kasey.umkc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=zbrown@tumblerings.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;
as well as URLs for NNTP newsgroup(s).