Question

Consider Unix, Linux, MacOS, Android and Windows operating systems. Consider the primary application of each in the marketplace. How does each OS implement threads? How does the usage of threads impact application (usage) ?

Answer 1

nux,MacOS,Android and Windows

Unix OS mostly used in modern servers,workstations and mobile servers. it plays a major role in TCP/IP networking protocol and also act as a backbone of the internet services such as chat,video conferencing etc.

Linux : Open source OS which is mainly focus on Web Serving,networking,databases,Scientific Computing etc.various popular companies like  Google, Amazone, Dreamworks are uses to ensure security and stability of their network.

Mac OS mainly focus on file sharing, network browsing, and multiple user accounts across the internet.

Android is a Linux based operating system designed for tablet computer and Smart phones.It controls the robotic vehicle using an android application. The remote operation is achieved by smart phone or tablet through touch screen

windows support automation of offline and online applications in the areas of e-commerce and e business.

Implementation of threads in Unix,Linux, Mac OS,Android, Windows

Implementation of threads in differ from OS to OS.

Unix

Linux

Creating a (default) thread Detaching a thread Terminating a thread

Linux implements all threads as standard processes. The Linux kernel does not provide any special scheduling semantics or data structures to represent threads. Instead, a thread is merely a process that shares certain resources with other processes. Each thread has a unique task_struct and appears to the kernel as a normal process (which just happens to share resources, such as an address space, with other processes)

Mac OS

Android

Creating a Thread Creating low-level threads is relatively simple. In all cases, you must have a method to act as your thread’s main entry point and you must use one of the available thread routines to start your thread. Eg: NSThread class

threading components into two basic categories: Threads that are attached to an activity/fragment: These threads are tied to the lifecycle of the activity/fragment and are terminated as soon as the activity/fragment is destroyed. Threads that are not attached to any activity/fragment: These threads can continue to run beyond the lifetime of the activity/fragment (if any) from which they were spawned. AsyncTask is the most basic Android component for threading.

Windows

User(-level) threads – management by user-level threads library. Windows threads Java threads