> I would strongly suggest keeping as much code user-level as possible.
> Do use a special library until you have things working; once your code
> works, fold your special library into libc. Transparency takes time,
> and I was under the impression you wanted to get something working this
> decade...
I'm going to code a load _sharing_ mechanism, not a load _balancing_
mechanism. Balancing involves a policy and a sharing mechanism. My code
won't decide which process is good to migrate, it will only migrate
processes when told to. It will, of course, provide a way for a "policy
daemon" to comunicate with it and gather statistics on the usage of the
cluster of machines in a way that the policy will be absolutely platform
independent, and also communication mechanism independent, what means that
it will talk to the migration daemon through a high level message
interface.
The "policy daemon" would be another project, maybe even bigger. I'm going
to do as much as I can on user level, but keeping enough on the kernel so
that I can migrate even your getty if suddenly it starts consuming too
much resources :). (flame protection: that was a joke)
[]
Fabio
( Fabio Olive Leite leitinho@akira.ucpel.tche.br )
( Computing Science Student http://akira.ucpel.tche.br/~leitinho/ )
( )
( LOADLIN.EXE: The best Windows95 application. [Debian GNU/Linux] )