linux-kernel - Re: Would SSI clustering extensions be of interest to kernel community?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:  <4533B177.7030004@gmail.com>
Date:	Mon, 16 Oct 2006 21:51:11 +0530
From:	"Aneesh Kumar K.V" <aneesh.kumar@...il.com>
To:	linux-kernel@...r.kernel.org
Subject:  Re: Would SSI clustering extensions be of interest to kernel community?

Constantine Gavrilov wrote:
> I have implemented SSI (single system image) clustering extensions to 
> Linux kernel in the form of a loadable module.
> 
> It roughly mimics OpenMosix model of deputy/remote split (migrated 
> processes leave a stub on the node where they were born and depend on 
> the "home" node for IO).
> 
> The implementation shares no code with Mosix/Open Mosix (was written 
> from scratch), is much smaller, and is easily portable to multiple 
> architectures.
> 
> We are considering publication of this code and forming an open source 
> project around it.
> 
> I have two questions to the community:
> 
> 1) Is community interested in using this code? Do users require SSI 
> product in the era when everybody is talking about partitioning of 
> machines and not clustering?
> 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.)
> 
> Please CC me and the list when replying.
> 

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.

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. 

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.

-aneesh

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/