PID vs TID in Linux

-
PID Stands for Process ID and TID stands for Thread ID.

Each process in Linux Kernel is internally represented by task_struct (present in include/linux/sched.h)

To get the process ID, we call getpid() API in Linux and gettid() for thread ID.

Let's see what happens internally when we call this API.



From the screenshot, we can see that kernel returns pid member of the task_struct structure when we call gettid() and tgid member of the task_struct when we call getpid()


tgid -> Thread Group ID.

Difference between pid and tgid:

 Linux implements all threads as standard processes, Each thread will have an unique task_struct and appears to kernel as normal process, and share resources such as address space, open files etc with other processes.

The pid field in the task_struct is used to identify the thread of the process , and tgid is used to identify the pid of the thread which started the process

When a new process is created, the value of both tgid and pid will be same, only when a new thread is created in the code, pid of that thread will change but tgid will be same.

Code:

Output:

Notes:

1. man gettid tells you that "GLibc does not provide you a wrapper for this system call". So, we use syscall for calling gettid

Comments

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

PR, PN and PV Variable in Yocto

-
PN : Represents the name of the recipe. The name is usually extracted from the recipe file name. PR:  Represents the revision of the recipe. Default value for this revision is "r0". Subsequent revisions of the recipe conventionally will have "r1", "r2" and so on. PV:  Represents the version of the recipe. Normally extracted from the recipe file name. For example: ffmpeg_3.4.2.bb recipe. ${PN} : ffmpeg ${PV} : 3.4.2
Read more