Re: oM 2.6, let's get working, todolist ?
tab-mTI/[email protected] (Vincent Hanquez)
| Newsgroups | gmane.linux.cluster.openmosix.devel |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Jul 20, 2006 at 10:12:08AM +0200, Florian Delizy wrote: > - migrate a task from 'home' to a node > - migrate a task already moved on a node to another node (usefull for > kind of a defrag feature let's say ;) ) > - on a 64bit arch, ensure that 64bit and 32bit processes are migrated > correctly > - access any node CPU load informations (to allow a load balancing > program to work) > - as much bugfree as possible > > (that's for end of Setptember), when that will be done, I will also need > to do a kind of "failover" for master nodes (something like Linux HA, > the master creating processes dies, but processes running on other > nodes, created from there, get reassigned to a failover node), and also > look into the "software checkpoint" thing. This one is not yet > scheduled, but it has to be done I think before the end of October. > > My question is: > > Is it possible to make a todolist of what is left to be done, including > needed features and current bugs as well, so I can make a planning and > get my boss agreement ? * kcomd completion * migrating current API to kcomd * 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/ - known nodes export through /omctrlfs - 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) -- Vincent Hanquez ------------------------------------------------------------------------- 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