public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Marowsky-Bree <lmb@suse.de>
To: sdake@mvista.com,
	Discussion of clustering software components including GFS
	<linux-cluster@redhat.com>, Daniel Phillips <phillips@redhat.com>
Cc: 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 19:51:29 +0200	[thread overview]
Message-ID: <20040910175129.GT7359@marowsky-bree.de> (raw)
In-Reply-To: <1094104992.5515.47.camel@persist.az.mvista.com>

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?

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?

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>

-- 
High Availability & Clustering	   \\\  /// 
SUSE Labs, Research and Development \honk/ 
SUSE LINUX AG - A Novell company     \\// 


  reply	other threads:[~2004-09-10 20:31 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     ` [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 [this message]
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=20040910175129.GT7359@marowsky-bree.de \
    --to=lmb@suse.de \
    --cc=linux-cluster@redhat.com \
    --cc=linux-ha-dev@lists.linux-ha.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openais@lists.osdl.org \
    --cc=phillips@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox