Code: Select all
/----- User Process
Kernel ---- Drivers ------ Disk
\----- Graphics
\---- Input (keyboard/mouse,joystick)
Code: Select all
Kernel :
a.) memory manager
1.) virtual memory manager
a.) virtual -> physical mapper
b.) kernel allocator
1.) page allocator
2.) memory allocator (ala, malloc)
3.) process cleanup
c.) Demand page loading/page exception handling
d.) swap file/disk
2.) physical
a.) physical page allocation
b.) process manager
1.) thread manager
a.) thread list manager
b.) thread memory manager
1.) allocator
2.) cleanup
c.) thread scheduler
2.) process manager
a.) process list manager
b.) process memory manager
1.) process/kerel memory unifying (make sure the kernel mapping per thread is updated when the kernel map changes)
2.) process cleanup
c.) process scheduler (possibly same/similar to threads)
c.) function calls/interface
d.) interrupts
e.) timer
f.) drivers
g.) inter process comms
. If you are a micro kernel, you need a VERY robust process communication layout, because of all the context switching that is required, it is not efficient to go from process->kernel->process, imlpementing a way for one process to directly talk to another is very useful. With a monolithic kernel, the drivers run in kernel space, and thus can memory map userland space and use memory mappings to easily transfer data, so the amount of IPC can be much less/simpler (although, once you start running a GUI as a userland process, you definetely don' want your IPC being a POS either). So, give us a bit more information, and maybe we can give you a little more information that you're actually looking for.I was just kind of curious of how indepth you wanted the chart to get. I mean, do you want to list... Multiprocessing... or do you want to list: thread scheduler, process scheduler, process memory manager, etc, etc. I wasn't sure if you wanted to get down to the functions, or just the overall view of what the section is doing, etc. Security and minimum resources don't normally go together to nicely I'm affraid, typically all the bounds and checks, and seperation of processes means a lot of extra memory and cpu cycles. For example:parag wrote:Ready4Dis i like the systematic manner in which you have shown several ways of how a flowchart is made. but i am stressing on two points
1.using minimum resources
2.security
priorities being in that order