>
> So what if we have an IScheduler interface, and simply have multiple
> schedulers that inherit from this interface.
> Which scheduler is used could be configurable, and the right scheduler
> would be started at startup.
Yes, I agree. it have to be onfigurable because not only we need to test the
scheduler's performance but also have to be prepared for the various future
uses of SharpOS. I think it's good to start from a simple scheduler just
like FIFO. and then extends on.
>
> Anyway, we really need some sort of design for the kernel, because
> even at this semi "hello world" level it's starting to become rather
> chaotic.
how about to post a proposal for the scheduler or kernel design? then we can
dicuss about designing
of the scheduler or kernel together :)
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> SharpOS-Developers mailing list
> SharpOS-Developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sharpos-developers
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
