From: Constantine Gavrilov <constg@qlusters.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Would SSI clustering extensions be of interest to kernel community?
Date: Mon, 16 Oct 2006 19:47:02 +0200 [thread overview]
Message-ID: <4533C596.5060804@qlusters.com> (raw)
In-Reply-To: <4533B177.7030004@gmail.com>
Please see inline...
Aneesh Kumar K.V wrote:
>
> I am interested in seeing the changes. I am right now working on
> getting parts of OpenSSI (www.openssi.org)
> changes merged upstream. Bruce Walker of the OpenSSI project have a
> design of implementing cluster wide procs. The
> same doc can be found on www.openssi.org website. The paper talks
> about how to implement cluster wide proccess model
> without requiring home/deputy concept. But yes it require some core
> kernel changes. But should be Conditionally enabled
> like selinux. So overhead for non cluster users should be nill.
I am personally not interested in making intrusive kernel changes even
if it yields in true "single-system image". I want very small changes
(preferrably none).
>
> Regarding my work you can see the status here
> http://git.openssi.org/~kvaneesh/gitweb.cgi?p=ci-to-linus.git;a=summary
>
> It only gets the ICS changes. That means it introduce a transport
> independent kernel cluster framework. Right now it supports two
> interconnect IPV4 and infiniband verbs.
We also have transport abstraction layer and transport plugins for
TCP/IP, SDP (Infiniband and possibly others), and SCI (Dolphin).
> I am planning on taking the CFS changes. That should bring in
> clusterwide shared memory too. The way it was done in OpenSSI
> was to hook a new nopage() function for CFS so that when we page
> fault, we bring the pages from other node.So i am not sure whether
> one need a VM hook for getting clusterwide shared memory. But without
> seeing the code i am clueless.
>
Nopage will be called if there is no pte. That means, with just nopage
you cannot implement RO-RW transition. If you use nopage only, you
cannot have multiple readers, because you cannot invalidate all other
readers if one reader goes read-write. Thus nopage allows single reader
or single writer whle the page fault hook allows multiple readers and
single writer.
--
----------------------------------------
Constantine Gavrilov
Kernel Developer
Qlusters Software Ltd
1 Azrieli Center, Tel-Aviv
Phone: +972-3-6081977
Fax: +972-3-6081841
----------------------------------------
next prev parent reply other threads:[~2006-10-16 17:48 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
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 [this message]
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=4533C596.5060804@qlusters.com \
--to=constg@qlusters.com \
--cc=aneesh.kumar@gmail.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 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.