From: Steven Dake <sdake@mvista.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: Discussion of clustering software components including GFS
<linux-cluster@redhat.com>, Daniel Phillips <phillips@redhat.com>,
openais@lists.osdl.org, linux-ha-dev@lists.linux-ha.org,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-cluster] New virtual synchrony API for the kernel: was Re: [Openais] New API in openais
Date: Fri, 10 Sep 2004 13:53:15 -0700 [thread overview]
Message-ID: <1094849594.23862.184.camel@persist.az.mvista.com> (raw)
In-Reply-To: <20040910175129.GT7359@marowsky-bree.de>
On Fri, 2004-09-10 at 10:51, Lars Marowsky-Bree wrote:
> On 2004-09-01T23:03:12,
> Steven Dake <sdake@mvista.com> said:
>
> I've been pretty busy the last couple of days, so please bear with me
> for my late reply.
>
> A virtual synchrony group messaging component would certainly be
> immensely helpful. As it pretty strongly ties to membership events (as
> you very correctly point out), I do think we need to review the APIs
> here.
>
> Could you post some sample code and how / where you'd propose to merge
> it in?
>
The virtual synchrony APIs I propose we start with can be reviewed at:
http://developer.osdl.org/dev/openais/htmldocs/index.html
There is a sample program using these interfaces at:
http://developer.osdl.org/dev/openais/src/test/testevs.c
> Also, again, I'm not sure this needs to be in the kernel. Do you have
> upper bounds of the memory consumption? Would the speed really benefit
> from being in the kernel?
>
Right now, the entire openais project with all the services it provides
consumes 2MB of ram at idle. I'd expect under load its about 3MB. The
group messaging protocol portion of that uses perhaps 1 MB of ram. It
will reject new messages if its buffers are full, so it cannot grow
wildly.
Your definately correct; a virtual syncrhony protocol doesn't absolutely
have to be in the kernel. In fact, it is implemented today completely
in userland with 8.5MB/sec throughput to large groups with encryption
and authentication.
You could gain some network performance by ridding UDP from the IP
header, but this is only 8 bytes.
There is little performance gain in using the kernel (as basically, a
kernel thread/process would have to be created to operate the protocol).
The only point of a kernel virtual syncrhony API is to standardize on
one set of messaging APIs for the kernel projects that require messaging
(and at a higher level, distributed locks, fencing, etc).
We want to avoid is two seperate messaging protocols operating at the
same time (performance drain).
We also want to choose wisely the messaging model and protocol we use.
If we don't, we could have problems later.
> OTOH, all other networking protocols such as TCP, SCTP or even IP/Sec
> live in kernel space, so clearly there's prior evidence of this being a
> reasonable idea.
>
>
> Sincerely,
> Lars Marowsky-Brée <lmb@suse.de>
prev parent reply other threads:[~2004-09-10 20:54 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
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 [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=1094849594.23862.184.camel@persist.az.mvista.com \
--to=sdake@mvista.com \
--cc=linux-cluster@redhat.com \
--cc=linux-ha-dev@lists.linux-ha.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=openais@lists.osdl.org \
--cc=phillips@redhat.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 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®