Re: thread awareness of the scheduler

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jan Hudec wrote:
Yes. And it is the *SOLE* reason for the difference in ps output. Well,
in fact, the manager thread is also gone and some ABI is being used so
it's all faster. But the basic principle -- that each thread is
a process -- has not changed.

The term "process" is used inappropriately, or as a shorcut to the more appropriate term "Linux kernel schedulable entity".


A process is a collection of resources, which include executable image (a.k.a. program), address space, file descriptors, environment variables, current working directory, atexit cleanup handlers[1], etc. A process is a place, not an activity. OTOH, a thread is an activity, which happens in a particular place, i.e. process. Threads share the abovementioned resources, thus they are part of the same process and are not processes themselves.

Thus the above "principle" is not and was never true, according to the established[2] definition of "process". It's simply someone choose to call threads "processes", but forgot to invent a term for processes.

~velco

[1] I know I mix kernel and userlevel resources, but this distinction is
    conceptually irrelevant.
[2] "An address space with one or more threads executing within that
     address space, and the required system resources for those
     threads."
    IEEE Std 1003.1-2001

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux