Back on Sunday 18 May 2008, Paul Davis was like:
On Sat, 2008-05-17 at 19:12 -0500, Reuben Martin
wrote:
I guess I just wasn't aware that there are 4
separate jackd processes
that run. That makes a lot more sense now.
terminology (simplified)
"TASK" : a kernel-level thread
"THREAD" : a user-space thread
"PROCESS" : 1 or more threads, plus an
address space and a file table
JACK is a single process involving multiple threads.
--p
Why then are the threads assigned separate PIDs? I was under the assumption
that PID stood for "Process Identifier". (Perhaps "Posix thread
IDentifier"
would be a better definition of the acronym) I was totally unaware that you
could assign process threads separate scheduling priorities / policies apart
from the parent process.
Also, is it possible (within the context of programming) to assign threads
individual names to give an indication as to what the specific PID is doing,
or are thread PID names always named the same as the parent process?
I'm sure these questions open up a whole can of worms dealing with the mess of
conforming modern programming concepts to an aging POSIX framework.
-Reuben