


How to check which CPU a process is on in Linux
Viewing method: 1. Use the top command, which can display which CPU the process is running on. The syntax is "top -p process number"; 2. Use the taskset command, which is used to view processes or threads. Which CPU it is running on, the syntax is "tasksset -p process number".
#The operating environment of this tutorial: linux7.3 system, Dell G3 computer.
How to check which CPU the process is running on in Linux
Method 1: Use the top command
The top command can display which CPU the process is running on. You can Continuously monitor whether the CPU on which the process is running changes over time.
Usage steps:
top -p [进程号],例如 top -p 3000
Press the "F" key, use the up and down keys to select P = Last Used Cpu, and press the space bar. "*" appears to indicate selection, and then press " q"Exit.
Method 2: Use the taskset command
taskset can check which CPU a specific process (or thread) is running on, and can also make a certain program run on a certain CPU.
taskset parameter options on one or some CPUs:
(1) -p, --pid: operate the existing PID and do not start a new task
(2 ) -c, --cpu-list: Specify a numerical list of processors instead of a bitmask. The list can contain multiple items, separated by commas and ranges. For example, 0, 5, 7, 9 - 11.
1) Display the CPU on which the process is running: -p parameter
Example 1:
[root@localhost ~]# taskset -p 21184
Display result:
pid 21184’s current affinity mask: ffffff
Note: 21184 is the process number. The ffffff that displays the result is actually a bitmask in which the 24 low-order bits of the binary are all 1. Each 1 corresponds to 1 CPU, indicating that the process is running on 24 CPUs.
Example 2:
[root@localhost ~]# taskset -p 2030
Display results:
pid2030’s current affinity mask: f
Note: It means that sshd randomly switches on 4 CPUs.
Example 3:
[root@localhost ~]# taskset -p 2726
Display result:
pid 2726’s current affinity mask: 3
Note: The displayed decimal number 3 is converted to binary, and the lowest two are 1, and each 1 corresponds to one cpu, so the process runs on 2 cpu.
*Note: *The cpu label starts from 0, so cpu1 represents the second cpu (the first cpu label is 0).
About the conversion method
CPU ID of 8 cores: 7 6 5 4 3 2 1 0
Corresponding decimal digit of 10: 128 64 32 16 8 4 2 1
The 16 numbers in hexadecimal are: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E. F
corresponds to each hexadecimal binary digit: 0=0000,1=0001,2=0010,3=0011,4=0100,5=0101,6=0110,7=0111, 8=1000,9=1001,A=1010,
B=1011,C=1100,D=1101,E=1110,F=1111
Then for example, pid 8987's current affinity appears mask: ff ff is hexadecimal, converted to binary: 11111111, which means that sshd is executed on 8 CPUs! So corresponding to each value!
For example, 40 in hexadecimal, then convert binary 01000000, which means operating on the 7th CPU
Recommended learning: Linux video tutorial
The above is the detailed content of How to check which CPU a process is on in Linux. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

VS Code To switch Chinese mode: Open the settings interface (Windows/Linux: Ctrl, macOS: Cmd,) Search for "Editor: Language" settings Select "Chinese" in the drop-down menu Save settings and restart VS Code

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.
