On 9/23/07, Darx Kies <[EMAIL PROTECTED]> wrote: > I don't want to talk the importance of the scheduler down, or the work > that Sander van Rossen did (which is fantastic). > But we should concentrate more on the Memory Manager, as > a single threaded/single process for the 0.0.1 release is ok, IMHO.
It's no problem and i agree that we need to concentrate on a memory manager at the moment.. in fact, i can't actually continue with the scheduler untill we have some heap memory management ;) The reason i was working on a scheduler was because a garbage collector would need to run in a seperate thread, and it would also help in abstracting the drivers.. I guess this isn't so important for the 0.01 release, but i was just looking ahead to keep myself busy while i was waiting for the AOT problems to be resolved (i have no time at the moment to dive into AOT land, hopefully start of next month things will quiet down for me at work).. and the scheduler was kinda the result of that. > PS: The AOT generates now a PE for the kernel only. Generating PE for > other purposes is > possible, though there are a couple of things that are still missing > (e.g. relocations and so on). Allright, it might eventually be usefull to include basic drivers (disk io / keyboard etc.) in the kernel by compiling them with the AOT and including them into the kernel as resources.. which would make it easier to seperate them from the kernel. ------------------------------------------------------------------------- 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
