mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: shogunx <shogunx@sleekfreak.ath.cx>
To: Christian <christiand59@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Integration of clustering (mosix) into mainline
Date: Mon, 27 Feb 2006 14:04:40 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0602271354020.28982-100000@sleekfreak.ath.cx> (raw)
In-Reply-To: <200602271638.11147.christiand59@web.de>

On Mon, 27 Feb 2006, Christian wrote:

Hi Christian,

> I just wondered if there is any interest in integrating a technology like
> OpenMosix into mainline. This would make more sense than ever, especially
> with the virtualization work going on now. What objections do you feel, and
> what amount of work would it be?

I have an interest in such.  I agree that xen/openmosix is a powerful
combo, one that would give linux mainframe-like capabilities,
(i know, i know, there is linux support for s/390, in fact, I
own such a mainframe, but there is no Xen for linux/390, and
most linux/390 images run in vm's anyway) particularly
with the addition of OM for scalability.  Amount of work?  On x86, the 2.6
OM branch is (relatively) stable as a set of patches now, but the entire
suite is not finished yet.  The kernel code is functional, though, being
massaged, something that would no doubt be better off with the help of
mainline kernel developers.  As of yet there are no userspace apps, such
as an automigration daemon, that are necessary to have a fuctional OM
cluster that actually migrates processes.  The biggest hurdle I see to
inclusion in the mainline kernel is the support for previously
non-supported architectures... though I would love to add my alphaservers
to my OM cluster:)  Once again, these ports could probably be lubricated
with the help of mainline kernel developers with specific knowledge and
experience on these platforms.

I hope that helps,
Scott


>
> Just curious...
>
> -Christian
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

sleekfreak pirate broadcast
http://sleekfreak.ath.cx:81/


      reply	other threads:[~2006-02-27 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 15:38 Christian
2006-02-27 19:04 ` shogunx [this message]

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.44.0602271354020.28982-100000@sleekfreak.ath.cx \
    --to=shogunx@sleekfreak.ath.cx \
    --cc=christiand59@web.de \
    --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

all inboxes | Powered by JetHome®