Timeline for Does the definition of a thread in Linux depend on a system call?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 22, 2023 at 18:02 | comment | added | Philip Couling | @Kolay.Ne now I re-read everything and your question I think the posix definition should be taken elsewhere. Thus whatever flags pthread_create passes in Linux implementations. I don't have that list. Beyond that read mix/match flags as undefined or undocumented. | |
| Jul 22, 2023 at 17:55 | history | edited | Philip Couling | CC BY-SA 4.0 | added 472 characters in body |
| Jul 22, 2023 at 16:55 | comment | added | Kolay.Ne | Okay, thank you for the historical context. However, this still does not help me in understanding manuals for system calls that don't have to do with threads creation. For instance, a practical question that I might have: if I use a futex to synchronize tasks that were created with CLONE_VM and without CLONE_THREAD, would it be safe (and, preferably, portable to future Linux versions) to use _PRIVATE futex operations in that case? | |
| Jul 22, 2023 at 16:38 | comment | added | ilkkachu | The actual current Linux implementation doesn't exactly fit the common processes/threads terminology, since (as the Q says), there's no strict division between the two wrt. sharing VM and fds etc. so you can have distinct "processes" that share some things, or "threads" that don't. (I'd have to check the details.) The clone() man page likely uses different terminology exactly because it describes the Linux implementation, while the others assume the more commonly used terminology. | |
| Jul 22, 2023 at 16:37 | comment | added | ilkkachu | From the discussion in the linked Q&A (and some other sources there), I gather that it's more a distinction between the terminology within the Linux kernel implementation (thread groups that contain processes), vs. the more usual terminology used, well, everywhere else, including the Linux userspace (processes containing threads) rather than a distinction between old and new. Though of course the history of the old non-POSIX implementation in Linux is the background to all that. | |
| Jul 22, 2023 at 16:24 | history | edited | Philip Couling | CC BY-SA 4.0 | added 245 characters in body |
| Jul 22, 2023 at 16:16 | history | answered | Philip Couling | CC BY-SA 4.0 |