From: Daniel Phillips <phillips@redhat.com>
To: linux-cluster@redhat.com, sdake@mvista.com
Cc: John Cherry <cherry@osdl.org>,
openais@lists.osdl.org, linux-kernel@vger.kernel.org,
linux-ha-dev@new.community.tummy.com
Subject: Re: [Linux-cluster] New virtual synchrony API for the kernel: was Re: [Openais] New API in openais
Date: Wed, 1 Sep 2004 11:06:00 -0400 [thread overview]
Message-ID: <200409011106.00541.phillips@redhat.com> (raw)
In-Reply-To: <1093981842.3613.42.camel@persist.az.mvista.com>
Hi Steven,
On Tuesday 31 August 2004 15:50, Steven Dake wrote:
> It would be useful for linux cluster developers for a common low
> level group communication API to be agreed upon by relevant clusters
> projects. Without this approach, we may end up with several systems
> all using different cluster communication & membership mechanisms
> that are incompatible.
To be honest, this does look interesting, however could you help me on a
few points:
- Is there any evil IP we have to worry about with this?
- Can I get a formal interface spec from AIS for this, without
signing a license?
- Have you got benchmarks available for control and normal messaging
next prev parent reply other threads:[~2004-09-01 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1093941076.3613.14.camel@persist.az.mvista.com>
[not found] ` <1093973757.5933.56.camel@cherrybomb.pdx.osdl.net>
2004-08-31 19:50 ` New virtual synchrony API for the kernel: was Re: [Openais] New API in openais Steven Dake
2004-09-01 15:06 ` Daniel Phillips [this message]
2004-09-01 15:15 ` [Linux-cluster] " Daniel Phillips
2004-09-01 20:57 ` John Cherry
2004-09-02 6:03 ` Steven Dake
2004-09-10 17:51 ` Lars Marowsky-Bree
2004-09-10 20:53 ` Steven Dake
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=200409011106.00541.phillips@redhat.com \
--to=phillips@redhat.com \
--cc=cherry@osdl.org \
--cc=linux-cluster@redhat.com \
--cc=linux-ha-dev@new.community.tummy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openais@lists.osdl.org \
--cc=sdake@mvista.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.