پاورپوینت کامل comparing windows XP and Linux 48 اسلاید در PowerPoint

توجه : این فایل به صورت فایل power point (پاور پوینت) ارائه میگردد

 پاورپوینت کامل comparing windows XP and Linux 48 اسلاید در PowerPoint دارای ۴۸ اسلاید می باشد و دارای تنظیمات کامل در PowerPoint می باشد و آماده ارائه یا چاپ است

شما با استفاده ازاین پاورپوینت میتوانید یک ارائه بسیارعالی و با شکوهی داشته باشید و همه حاضرین با اشتیاق به مطالب شما گوش خواهند داد.

لطفا نگران مطالب داخل پاورپوینت نباشید، مطالب داخل اسلاید ها بسیار ساده و قابل درک برای شما می باشد، ما عالی بودن این فایل رو تضمین می کنیم.

توجه : در صورت  مشاهده  بهم ریختگی احتمالی در متون زیر ،دلیل ان کپی کردن این مطالب از داخل فایل می باشد و در فایل اصلی پاورپوینت کامل comparing windows XP and Linux 48 اسلاید در PowerPoint،به هیچ وجه بهم ریختگی وجود ندارد

بخشی از مطالب داخلی اسلاید ها

پاورپوینت کامل comparing windows XP and Linux 48 اسلاید در PowerPoint

اسلاید ۴: ۴Linus and LinuxIn 1991 Linus Torvalds took a college computer science course that used the Minix operating systemMinix is a “toy” UNIX-like OS written by Andrew Tanenbaum as a learning workbenchLinus wanted to make MINIX more usable, but Tanenbaum wanted to keep it ultra-simpleLinus went in his own direction and began working on LinuxIn October 1991 he announced Linux v0.02In March 1994 he released Linux v1.0

اسلاید ۵: ۵Windows and LinuxBoth Linux and Windows are based on foundations developed in the mid-1970s1970198019902000UNIX bornUNIX publicUNIX V6Linux v1.0v2.0v2.1v2.2v2.3v2.4v2.61970198019902000VMS v1.0Windows NT 3.1 NT 4.0Windows 2000Windows XPServer 2003

اسلاید ۶: ۶Comparing the ArchitecturesBoth Linux and Windows are monolithicAll core operating system services run in a shared address space in kernel-modeAll core operating system services are part of a single moduleLinux: vmlinuz Windows: ntoskrnl.exeWindowing is handled differently:Windows has a kernel-mode Windowing subsystemLinux has a user-mode X-Windowing system

اسلاید ۷: ۷Kernel ArchitecturesDevice DriversProcess Management, Memory Management, I/O Management, etc.X-WindowsApplicationSystem ServicesUser ModeKernel ModeHardware Dependent CodeLinuxDevice DriversProcess Management, Memory Management, I/O Management, etc.Win32WindowingApplicationSystem ServicesUser ModeKernel ModeHardware Dependent CodeWindows

اسلاید ۸: ۸Linux KernelLinux is a monolithic but modular systemAll kernel subsystems form a single piece of code with no protection between themModularity is supported in two ways:Compile-time optionsMost kernel components can be built as a dynamically loadable kernel module (DLKM)DLKMsBuilt separately from the main kernel Loaded into the kernel at runtime and on demand (infrequently used components take up kernel memory only when needed)Kernel modules can be upgraded incrementallySupport for minimal kernels that automatically adapt to the machine and load only those kernel components that are used

اسلاید ۹: ۹Windows KernelWindows is a monolithic but modular systemNo protection among pieces of kernel code and driversSupport for Modularity is somewhat weak:Windows Drivers allow for dynamic extension of kernel functionalityWindows XP Embedded has special tools / packaging rules that allow coarse-grained configuration of the OSWindows Drivers are dynamically loadable kernel modulesSignificant amount of code run as drivers (including network stacks such as TCP/IP and many services)Built independently from the kernelCan be loaded on-demandDependencies among drivers can be specified

اسلاید ۱۰: ۱۰Comparing PortabilityBoth Linux and Windows kernels are portableMainly written in CHave been ported to a range of processor architecturesWindowsi486, MIPS, PowerPC, Alpha, IA-64, x86-64Only x86-64 and IA-64 currently supported> 64MB memory requiredLinuxAlpha, ARM, ARM26, CRIS, H8300, i386, IA-64, M68000, MIPS, PA-RISC, PowerPC, S/390, SuperH, SPARC, VAX, v850, x86-64DLKMs allow for minimal kernels for microcontrollers> 4MB memory required

اسلاید ۱۱: ۱۱Comparing Layering, APIs, ComplexityWindowsKernel exports about 250 system calls (accessed via ntdll.dll)Layered Windows/POSIX subsystems Rich Windows API (17 500 functions on top of native APIs)LinuxKernel supports about 200 different system callsLayered BSD, Unix Sys V, POSIX shared system librariesCompact APIs (1742 functions in Single Unix Specification Version 3; not including X Window APIs)

اسلاید ۱۲: ۱۲Comparing ArchitecturesProcesses and schedulingSMP supportMemory managementI/OFile CachingSecurity

اسلاید ۱۳: Windows Operating System Internals – by David A. Solomon and Mark E. Russinovich with Andreas PolzeProcess Management

اسلاید ۱۴: ۱۴Process ManagementWindowsProcessAddress space, handle table, statistics and at least one threadNo inherent parent/child relationshipThreadsBasic scheduling unitFibers – cooperative user-mode threadsLinuxProcess is called a TaskBasic Address space, handle table, statisticsParent/child relationshipBasic scheduling unitThreadsNo threads per-seTasks can act like Windows threads by sharing handle table, PID and address spacePThreads – cooperative user-mode threads

اسلاید ۱۵: ۱۵Scheduling PrioritiesWindowsTwo scheduling classes“Real time” (fixed) – priority 16-31Dynamic – priority 1-15Higher priorities are favoredPriorities of dynamic threads get boosted on wakeupsThread priorities are never lowered3115160FixedDynamicI/OWindows

اسلاید ۱۶: ۱۶Scheduling PrioritiesWindowsTwo scheduling classes“Real time” (fixed) – priority 16-31Dynamic – priority 1-15Higher priorities are favoredPriorities of dynamic threads get boosted on wakeupsThread priorities are never loweredLinuxHas 3 scheduling classes:Normal – priority 100-139Fixed Round Robin – priority 0-99Fixed FIFO – priority 0-99Lower priorities are favored Priorities of normal threads go up (decay) as they use CPUPriorities of interactive threads go down (boost)

اسلاید ۱۷: ۱۷Scheduling Priorities (cont)3115160FixedDynamicI/OWindows14010d FIFOFixed Round-RobinNormalCPUI/OLinux

اسلاید ۱۸: ۱۸Linux Scheduling DetailsMost threads use a dynamic priority policy Normal class – similar to the classic UNIX schedulerA newly created thread starts with a base priority Threads that block frequently (I/O bound) will have their priority gradually increasedThreads that always exhaust their time slice (CPU bound) will have their priority gradually decreased“Nice value” sets a thread’s