why not random migration algorithm?

Hi all developers,
	Every once in awhile I hear that you all are working on porting 2.4's auto 
migration algorithm to 2.6, but people are busy, etcetera.
	Why not implement a random migration algorithm right now and make it smarter 
later?  This would at least allow people to test the migration daemon's 
ability to migrate processes and the kernel-side stuff.
	Once there is some daemon code that is able move processes around without 
problem, people will be able to use the "random" (or other kind of simple) 
code as an example to write smarter policies.

Thanks for your hard work,
	C. 


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl