From: Steven Dake <sdake@mvista.com>
To: John Cherry <cherry@osdl.org>
Cc: openais@lists.osdl.org, linux-ha-dev@lists.linux-ha.org,
linux-cluster@redhat.com, linux-kernel@vger.kernel.org
Subject: New virtual synchrony API for the kernel: was Re: [Openais] New API in openais
Date: Tue, 31 Aug 2004 12:50:43 -0700 [thread overview]
Message-ID: <1093981842.3613.42.camel@persist.az.mvista.com> (raw)
In-Reply-To: <1093973757.5933.56.camel@cherrybomb.pdx.osdl.net>
John,
As it appears the redhat clusters project is interested in a kernel
implementation of cluster messaging, this interface would have to be
available to both the kernel and user applications. It possible to
provide EVS services to both kernel and user space applications. There
currently is no kernel implementation of group messaging, though only a
user space interface. TIPC could probably export this sort of
interface, or openais's gmi could be ported to the kernel. Then
openais, redhat's cluster technologies, linux ha, or other group
messaging applications (and there are quite a few) could use that
technology and standardize on the EVS API.
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.
Thanks
-steve
On Tue, 2004-08-31 at 10:35, John Cherry wrote:
> Steve,
>
> This sounds like a low level cluster communication service which would
> be potentially leveraged by other services, such as the event service or
> a group messaging service. Are you envisioning this to be a public
> interface for applications?
>
> We discussed a low level cluster communication interface at the cluster
> summit. The rhat/sistina interface would be used by the cluster manager
> (CMAN) and the lock manager (GDLM), but there was no real momentum to
> make this a public application interface. It would be great if we could
> derive a common cluster communication interface with the rhat/sistina
> project as well as the TIPC project. What do you think?
>
> John
>
>
> On Tue, 2004-08-31 at 01:31, Steven Dake wrote:
> > Folks
> >
> > Its with alot of pleasure that I announce a new API that I implemented
> > over the weekend.
> >
> > The api is called the "EVS" API and is provided by a seperate library
> > libevs.so/.a. The standard openais executive is used. There are two
> > test programs testevs and evsbench which demonstrate the API. evsbench
> > will benchmark throughput rates. I get about 9MB/sec on my hardware,
> > however, flow control in the group messaging protocol is slowing this
> > down. I've gotten 10MB/sec with tweaking the algorithm some.
> >
> > The API name EVS means "Extended Virtual Syncrhony". This API provides
> > EVS semantics for those that require the guarantees provided in the face
> > of partitions and merges.
> >
> > The API provides the following
> > multiple instances may exist at one time
> > group keys of 32 bytes
> > an instance may join one or more groups at one time
> > an instance may leave one or more groups at one time
> > an instance may multicast to the currently joined groups
> > an instance may multicast to unjoined groups
> > any message for a joined group will be delivered via callback
> > configuration changes are delivered via callback
> >
> > Your comments welcome
> >
> > Thanks
> > -steve
> >
> >
> > ______________________________________________________________________
> > _______________________________________________
> > Openais mailing list
> > Openais@lists.osdl.org
> > http://lists.osdl.org/mailman/listinfo/openais
>
next parent reply other threads:[~2004-08-31 20:00 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 ` Steven Dake [this message]
2004-09-01 15:06 ` [Linux-cluster] " Daniel Phillips
2004-09-01 15:15 ` 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=1093981842.3613.42.camel@persist.az.mvista.com \
--to=sdake@mvista.com \
--cc=cherry@osdl.org \
--cc=linux-cluster@redhat.com \
--cc=linux-ha-dev@lists.linux-ha.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openais@lists.osdl.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®