Re: oM 2.6, let's get working, todolist ?

Is this in the Wiki or anywhere online, so we can keep it updated?

<snip>
> 
> * kcomd completion
in progress.
> * migrating current API to kcomd
in progress.
> * handle execve_on_remote correctly.
> * simplify fork_on_remote thanks to kcomd.
> * fix process coming back when there's a problem (unsupported syscall,
>   etc...) on the remote
> * completion of process, doesn't return back the exit value to deputy.
> - fix some _user macro that are not supposed to sleep to work with
kcomd
>   (workaround already there AFAIK)
> - move /proc use to /omctrfs/

Where is the 'where' file located?

> - known nodes export through /omctrlfs
Is this still the planned structure?
http://sourceforge.net/mailarchive/forum.php?thread_id=11584308&forum_id=7969


> - move nodes structure to reference count.
> - handle 32 bit migrated process on 64 bit
> - fix remote to remote. will be easier with kcomd.
> 
> '*' are mandatory
> 
> access to remote cpus information, are to be done through userspace.
> specially since the kernelspace has no idea on the real map of nodes.
> kernel has a narrow view of the map, which consist on only the nodes
> it is communicating with (processes migrated to or from this node)
> 

Thoughts on this idea?
http://www.osource.org/openmosix/balancer.php


Matt


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV