*Rani of Hearts-Reena Kapoor Paristan#55*The Cave Woman - Page 4

(aaa shit here we go again 😆)

monolithic: OS runs as single program

pros:

-efficiency

cons:

-single point of failure

-no information hiding -> same address space shared

-difficult to understand

microkernel: OS divided into small modules

-microkernel runs in kernel mode.. rest run as user mode

-removes all non essential components from kernel

pros:

-more secure and reliable

-extending /adding new services is easier ->kernel isnt disturbed

-easier to port bcz kernel is small

cons:

-low performance -> bcz modules call each other (via kernel) -> no direct communication (i guess)

-cache misses

-TLB flushes

-IPC communication accross services (slowed down i guess)

-context switching

Mach (mk) - 900 cycles

-focused on portability

-lost locality

-didn't take advantage of hardware

so microsoft doesnt use microkernel 😲 so OS remains efficient

Mac uses it 😆and its blind users say it never crashes.. but they dnt know why it never crashes.. bcz its slower lolol😆

loadable kernel - a module in core kernel

similar to microkernel

The idea of the design is for the kernel to provide core services whileother services are implemented dynamically, as the kernel is running.

exokernel: allocates resources to virtual machines making sure none of them shares resources

reincarnation server (in minix3): checks if drivers are working correctly.. replaces faulty driver without user intervention.

how hypervisor supports illusion to VM?

shadow page table that instead maps the virtual addresses of each processto the VMM’s desired machine pages

Originally posted by: MasoomaBukhari

yes im gonna continue studying here only.. sorry replies baad me

@replies- koi masla nhi hai😃

Originally posted by: MasoomaBukhari

so microsoft doesnt use microkernel 😲 so OS remains efficient

Mac uses it 😆and its blind users say it never crashes.. but they dnt know why it never crashes.. bcz its slower lolol😆

PS - why lol is near rofl now @emojis