Process Threads - Process Utilization

A thread is an execution flow scheduled within a process. Every running process has at least one thread, and a multithreaded process has several flows that can make progress concurrently.

Processes and Threads

Threads in one process share resources such as the virtual address space and open file descriptors. Each thread still has its own execution state, including registers and a stack. Sharing makes communication efficient, but it also means an unsynchronized change by one thread can affect the others.

Separate processes normally have distinct address spaces and communicate through explicit interprocess mechanisms. Neither design is automatically faster or safer; the workload and implementation determine the trade-off.

CheckWhich resource is normally shared by threads in the same process?

Thread Identifiers

Linux represents each thread as a schedulable task with its own thread ID. The thread-group leader's ID is commonly presented as the process ID, while all members share a thread-group ID. Tools use labels such as PID, TID, LWP, and SPID; check the tool's field definitions instead of assuming every label means the same thing.

CheckWhat does each thread maintain independently?

Listing Threads with ps

Use explicit output fields to avoid ambiguous default layouts:

$ ps -eLo pid,tid,psr,stat,comm

On procps ps, -L shows threads and -e selects all processes. pid identifies the thread group, tid identifies an individual thread, psr shows the CPU on which it last ran, and stat reports state. To inspect one process:

$ ps -L -p 1234 -o pid,tid,stat,pcpu,comm

Thread listings are snapshots. A thread can exit or change state immediately afterward.

CheckWhich command lists threads belonging to PID 1234 with explicit fields?

Interpreting Thread Activity

High CPU in one thread can be hidden by a process-wide average. Combine thread-level CPU samples with application logs, stack traces, and profiling tools. Do not attach debuggers or send signals to production tasks without understanding pause, permission, and service impacts.

CheckWhy should a ps thread listing not be treated as permanent state?

Summary

You can now distinguish process resources from per-thread execution state.

Recognize that every process has at least one thread.
Identify resources shared by threads in one process.
List explicit process and thread IDs with ps -L.
Treat thread output as a snapshot and correlate it with other evidence.

Practice

In the practice terminal, run: ps -eLo pid,tid,psr,stat,comm It should list every process, one row per thread, with pid and tid columns.

ps -eLo pid,tid,... lists every thread.