What is lwp

Participation Threads. A Community Supported Knowledge-base. Login To Your Account. Forgot password. Pushpa Sharma 1. Vinove NKTiwari 3. Tiwari 5.

If you are knowledgeable about any fact, resource or experience related to this topic - please add your views using the reply box below.

For articles and copyrighted material please only cite the original source link. Each contribution will make this page a resource useful for everyone. What is the difference between policies, systems and procedures? Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search. I found an answer to the question here.

But I don't understand some ideas in the answer. For instance, lightweight process is said to share its logical address space with other processes.

What does it mean? I can understand the same situation with 2 threads: both of them share one address space, so both of them can read any variables from bss segment for example. But we've got a lot of different processes with different bss sections, and I don't know, how to share all of them. There is a difference between process - LWP lightweight process and user thread. I will leave process definition aside since that's more or less known and focus on LWP vs user threads.

LWP is what essentially are called today threads. Originally, user thread meant a thread that is managed by the application itself and the kernel does not know anything about it. LWP, on the other hand, is a unit of scheduling and execution by the kernel.

Example: Let's assume that system has 3 other processes running and scheduling is round-robin without priorities. Option 1. You have 2 user threads using one LWP. You have 2 LWP. Totally there are 5 LWP running. There are definitely more differences, but please, refer to slides. After posting, I found a good article that explains everything in more details and is in better English than I write. Processes exist in the operating system and correspond to what users see as programs or applications.

A thread, on the other hand, exists within a process. For this reason, threads are sometimes referred to as light-weight processes. Each process consists of one or more threads. Based on Tanenbaum's book "Distributes Systems", light weight processes is generally referred to a hybrid form of user-level thread and kernel-level thread. In addition each LWP can be running its own user-level thread. Multi-threaded applications are constructed by creating threads with thread library package , and subsequently assigning each thread to an LWP.

The biggest advantage of using this hybrid approach is that creating, destroying, and synchronizing threads is relatively cheap and do not need any kernel intervention. Beside that, provided that a process has enough LWPs, a blocking system call will not suspend the entire process.

If I'm not mistaken, you can attach user threads to a single LWP to potentially increase the level of concurrency without involving a system call. Thread is basically task assigned with one goal and enough information to perform a specific task.

Physical Therapy. Physical Training. Patient Technician. Post Therapy. Browse Abbreviations. Get instant explanation for any acronym or abbreviation that hits you anywhere on the web! Two clicks install ». Download Close. Lotus Word Pro Computing » Software -- and more Rate it:. Light Weight Process Business » Products -- and more Lightweight Water Purifier Governmental » Environmental -- and more Limited War Plan Governmental » Military -- and more Living Waters Publications Community » Religion.

Live Work Play Miscellaneous » Unclassified. Louisville Writing Project Miscellaneous » Unclassified. Labor and Worklife Program Miscellaneous » Unclassified.

Laughing With Passion Miscellaneous » Unclassified. Lebanon Water Project Miscellaneous » Unclassified. Legacy Wealth Partners Miscellaneous » Unclassified.