From: Steven Dake <sdake@mvista.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: "Walker, Bruce J" <bruce.walker@hp.com>,
linux-kernel@vger.kernel.org, Chris Wright <chrisw@osdl.org>,
Discussion of clustering software components including GFS
<linux-cluster@redhat.com>,
dcl_discussion@osdl.org, cgl_discussion@osdl.org
Subject: Re: [Linux-cluster] Re: [cgl_discussion] Re: [dcl_discussion] Clustersummit materials
Date: Thu, 12 Aug 2004 10:42:16 -0700 [thread overview]
Message-ID: <1092332536.7315.1.camel@persist.az.mvista.com> (raw)
In-Reply-To: <20040812095736.GE4096@marowsky-bree.de>
On Thu, 2004-08-12 at 02:57, Lars Marowsky-Bree wrote:
> On 2004-08-11T11:46:03,
> Steven Dake <sdake@mvista.com> said:
>
> > If we can't live with the cluster services in userland (although I'm
> > still not convinced), then atleast the group messaging protocol in the
> > kernel could be based upon 20 years of research in group messaging and
> > work properly under _all_ fault scenarios.
>
> Right. Another important alternative maybe the Transis group
> communication suite, which has been released as GPL/LGPL now.
>
> This all just highlights that we need to think about communication some
> more before we can tackle it sensibly, but of course I'll be glad if
> someone proves me wrong and Just Does It ;-)
>
agreed... Transis in kernel would be a fine alternative to openais gmi
in kernel.
Speaking of transis, is the code posted anywhere? I'd like to have a
look.
Thanks
-steve
>
> Sincerely,
> Lars Marowsky-Brée <lmb@suse.de>
next prev parent reply other threads:[~2004-08-12 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3689AF909D816446BA505D21F1461AE4C75110@cacexc04.americas.cpqcorp.net>
2004-08-11 18:46 ` Steven Dake
2004-08-12 9:57 ` Lars Marowsky-Bree
2004-08-12 17:42 ` Steven Dake [this message]
2004-08-12 20:37 ` Lars Marowsky-Bree
2004-08-12 22:59 ` Steven Dake
2004-08-13 9:40 ` Lars Marowsky-Bree
2004-08-13 15:54 ` Jonathan Stanton
2004-08-13 20:30 ` Lars Marowsky-Bree
2004-08-13 22:53 ` Jonathan Stanton
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=1092332536.7315.1.camel@persist.az.mvista.com \
--to=sdake@mvista.com \
--cc=bruce.walker@hp.com \
--cc=cgl_discussion@osdl.org \
--cc=chrisw@osdl.org \
--cc=dcl_discussion@osdl.org \
--cc=linux-cluster@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
/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®