Thread: How was the cpu scheduling of the process implemented?

I'm guessing this is the article you refer to.
Scheduler-Related System Calls | The Linux Process Scheduler | InformIT

Clone the git if you want to search for things like nice()
sourceware.org Git - glibc.git/summary

1-1. I was wondering if developers put a system call in charge of CPU scheduling directly into the program file.
Yes.

1-2. Or when compiler C compiles the program file, I was wondering if compiler would add a separate system call in charge of CPU scheduling.
No.

1-3. The scheduling system call was implemented in the C library, so I couldn't see the scheduling system call with my eyes, but I was wondering if it was running.
If you want to see what your program does at the user-space to kernel-space interface, then strace is your friend.
strace(1) - Linux manual page

Thank you for your answer.
I'd like to ask a question about this answer.

1-1. I was wondering if developers put a system call in charge of CPU scheduling directly into the program file.
Yes.


If developers do not write a scheduling-related system call code in a program file, does the program's process not have CPU scheduling?

Of course it has scheduling.

It runs under the default scheduling of whatever OS it's running on.

The scheduler is in the kernel.

It's not duplicated in every single compiled program.

> Is there a separate process in the OS to manage the scheduling of such a process?
Sure,
linux/kernel/sched at master * torvalds/linux * GitHub

It's a long way down to the bottom of this rabbit hole.

Professor, let me ask you one more question.

Thank you for teaching me that the CPU scheduler was a process, not a program source code in the kernel.

I've learned that CPU scheduler is not a separate process at school.

Until now, I learned that CPU scheduler is a passive program source code in the kernel.

And I learned that each process is frequently caught in an interrupt, enters kernel mode, and executes CPU scheduler code in the kernel on its own at school.

I have a question here.

Even if user processes are frequently interrupted and enter kernel mode due to hardware signals,

I didn't write the source code for the user process to execute the CPU scheduler source code in the kernel.

By the way, how do processes execute the source code of the CPU scheduler in the kernel?

That's why I asked this question.

I knew the CPU scheduler was built into the kernel, but it wasn't a passive source code, it was a separate process.

At school, I learned that CPU scheduler is not a separate process, but a source code built into the kernel.

Thank you for teaching me that the CPU scheduler was a process, not a program source code in the kernel.


Then, When entering PS-ef instructions into the shell,

what are the PID and CMD of the CPU scheduler process?