public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Constantine Gavrilov <constg@qlusters.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Would SSI clustering extensions be of interest to kernel community?
Date: Mon, 16 Oct 2006 14:54:01 +0100	[thread overview]
Message-ID: <1161006841.24237.33.camel@localhost.localdomain> (raw)
In-Reply-To: <45337FE3.8020201@qlusters.com>

Ar Llu, 2006-10-16 am 14:49 +0200, ysgrifennodd Constantine Gavrilov:
> 2) Are kernel maintainers interested in clustering extensions to Linux 
> kernel? Do they see any value in them? (Our code does not require kernel 
> changes, but we are willing to submit it for inclusion if there is 
> interest.)

If they are doing SSI well and do not need core kernel changes then yes
they sound very interesting to me. Historically the big concern has
always been that things like this muck up the kernel core which affects
the other 99.99999% of users who don't want SSI clustering.

Alan


  reply	other threads:[~2006-10-16 13:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-16 12:49 Would SSI clustering extensions be of interest to kernel community? Constantine Gavrilov
2006-10-16 13:54 ` Alan Cox [this message]
2006-10-16 14:10   ` Would SSI clustering extensions be of interest to kernelcommunity? Constantine Gavrilov
     [not found]   ` <45339234.4050400@qlusters.com>
2006-10-16 14:44     ` Alan Cox
2006-10-16 13:57 ` Would SSI clustering extensions be of interest to kernel community? Diego Calleja
2006-10-16 14:24 ` Jesper Juhl
2006-10-16 16:21 ` Aneesh Kumar K.V
2006-10-16 17:47   ` Constantine Gavrilov
2006-10-17 10:56     ` Aneesh Kumar K.V
2006-10-23  8:17 ` Pavel Machek

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=1161006841.24237.33.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=constg@qlusters.com \
    --cc=linux-kernel@vger.kernel.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