Thread - Revision history

Jnc: Kernel threads; threads usually have stacks

2023-12-15T16:25:39Z

Kernel threads; threads usually have stacks

← Older revision		Revision as of 16:25, 15 December 2023
Line 1:		Line 1:
	The term '''thread''' does not have a generally accepted firm/strict definition, but it generally means an [[instruction]] [[execute\|execution]] locus which is less powerful (in terms of its capabilities) than a [[process]]; e.g. a thread will generally not have its own [[address space]].		The term '''thread''' does not have a generally accepted firm/strict definition, but it generally means an [[instruction]] [[execute\|execution]] locus which is less powerful (in terms of its capabilities) than a [[process]]; e.g. a thread will generally not have its own [[address space]].

	Threads are usually instantiated within a process, and share its [[memory]], [[input/output\|I/O]] channels, etc. ~~All the threads in~~ a ~~particular process exhibit~~ [[~~fate-sharing~~]]~~: if the process is terminated~~, ~~all~~ the ~~threads within~~ it ~~necessarily~~ are ~~also lost~~.		Threads are usually instantiated within a process, and share its [[memory]], [[input/output\|I/O]] channels, etc. Threads do seem to usually have individual, per-thread, [[stack]]s, so that a thread can cease executing while down a [[subroutine call]] chain, and later resume executing at the exact point where it paused. (Thread-like abstractions without stacks are sometimes called '''fibers'''.)

			All the threads in a particular process exhibit [[fate-sharing]]: if the process is terminated, all the threads within it necessarily are also lost.

	Threads are often, but not always, supported by the [[kernel]] of an [[operating system]]; e.g. the system's [[scheduler]] may be prepared to run threads. If not, a [[library]] included in the process may manage them.		Threads are often, but not always, supported by the [[kernel]] of an [[operating system]]; e.g. the system's [[scheduler]] may be prepared to run threads. If not, a [[library]] included in the process may manage them.

	In [[multi-processor]] systems where the kernel supports threads, it may be allowed for multiple threads in a single process to execute concurrently.		In [[multi-processor]] systems where the kernel supports threads, it may be allowed for multiple threads in a single process to execute concurrently.

			Threads may also exist as abstractions inside the kernel (named '''kernel threads'''), for use in structuring of work inside the kernel.

	{{semi-stub}}		{{semi-stub}}

			==See also==

			* [[Kernel process]]

	[[Category: OS Basics]]		[[Category: OS Basics]]

Jnc: +cat

2018-12-16T21:13:51Z

+cat

← Older revision		Revision as of 21:13, 16 December 2018
Line 8:		Line 8:

	{{semi-stub}}		{{semi-stub}}

			[[Category: OS Basics]]

Jnc: Add fate-sharing

2018-10-31T12:58:06Z

Add fate-sharing

← Older revision		Revision as of 12:58, 31 October 2018
Line 1:		Line 1:
	The term '''thread''' does not have a generally accepted firm/strict definition, but it generally means an [[instruction]] [[execute\|execution]] locus which is less powerful (in terms of its capabilities) than a [[process]]; e.g. a thread will generally not have its own [[address space]].		The term '''thread''' does not have a generally accepted firm/strict definition, but it generally means an [[instruction]] [[execute\|execution]] locus which is less powerful (in terms of its capabilities) than a [[process]]; e.g. a thread will generally not have its own [[address space]].

	Threads are usually instantiated within a process, and share its [[memory]], [[input/output\|I/O]] channels, etc. ~~They~~ are often, but not always, supported by the [[kernel]] of an [[operating system]]; e.g. the system's [[scheduler]] may be prepared to run threads. If not, a [[library]] included in the process may manage them.		Threads are usually instantiated within a process, and share its [[memory]], [[input/output\|I/O]] channels, etc. All the threads in a particular process exhibit [[fate-sharing]]: if the process is terminated, all the threads within it necessarily are also lost.

			Threads are often, but not always, supported by the [[kernel]] of an [[operating system]]; e.g. the system's [[scheduler]] may be prepared to run threads. If not, a [[library]] included in the process may manage them.

	In [[multi-processor]] systems where the kernel supports threads, it may be allowed for multiple threads in a single process to execute concurrently.		In [[multi-processor]] systems where the kernel supports threads, it may be allowed for multiple threads in a single process to execute concurrently.

	{{semi-stub}}		{{semi-stub}}

Jnc: An OK start

2018-10-30T20:22:32Z

An OK start

New page

The term '''thread''' does not have a generally accepted firm/strict definition, but it generally means an [[instruction]] [[execute|execution]] locus which is less powerful (in terms of its capabilities) than a [[process]]; e.g. a thread will generally not have its own [[address space]].

Threads are usually instantiated within a process, and share its [[memory]], [[input/output|I/O]] channels, etc. They are often, but not always, supported by the [[kernel]] of an [[operating system]]; e.g. the system's [[scheduler]] may be prepared to run threads. If not, a [[library]] included in the process may manage them.

In [[multi-processor]] systems where the kernel supports threads, it may be allowed for multiple threads in a single process to execute concurrently.

{{semi-stub}}