Any process does have a distinct address space from any other process which is not one of its children

Any process always has one single thread of execution

After init phase, processes that are created as user-space processes cannot execute in kernel space

One process in SCHED_RR will always have priority over any process in SCHED_OTHER

After init phase, processes that are created as kernel processes cannot execute in user-space

Processes are always created in the running state

A process created with maximal niceness in SCHER_OTHER may never be running.

Two processes of same priority in SCHED_FIFO will always have the same amount of CPU time

Javascript

Fortran

SQL

C

Objective-C

Swift

.NET

Java

Python

Kotlin

Rust

C#

Go

C++

Assembly language mnemonics

Mostly unknown since Linux Foundation has not disclosed information on this subject

ADA

cpuload

sysmon

ps

uptime

lsps

cpufreq

ls

top

provide exclusive access of critical sections of code to processes or threads

improve virtual memory performance with software-only implementation

provide sharing of library executable code pages between several processes or threads

provide mutual exclusion capabilities for threads of the same process

improve cache hit performance with software-only implementation

provide sharing of read-only memory pages between several processes or threads

ACL

CC

DAC

MAC

RBAC

CAG

SCHED_RR

SCHED_DEADLINE

SCHED_FIFO

SCHED_BASIC

SCHED_NONE

SCHED_OTHER

SCHED_PREEMPT

SCHED_NULL

2 Mbytes

1 Mbyte

16 Kbytes

4 Mbytes

512 bytes

20 Kbytes

32 Kbytes

network

user

other

list

group

admin

It allocates immediately only half of what is asked, and the other half later on

It allocates none of the memory asked for

It allocates memory when it is really used by the process

It allocates immediately all memory asked for

it allocates more than the amount of memory asked

It allocates the amount of memory depending on what other existing processes have been allocated

It allocates the amount of memory depending on what other existing processes have asked

It allocates the amount of memory depending on what other existing processes have used

Interrupt handlers are not interruptible in interrupt context

Interrupt handlers may only be preempted by the scheduler

Interrupt handlers must use busy loop to wait in interrupt context

Interrupt handlers are always executing on different CPUs than currently running processes

Interrupt handlers are not interruptible in process context

Interrupt handlers in process context have always higher priority than other tasks in process context

Interrupt handlers are not reschedulable in process context

Interrupt handlers cannot wait in interrupt context

Interrupt handlers in interrupt context have always higher priority than other tasks in process context

Interrupt handlers are not reschedulable in interrupt context

Interrupt handlers are not preemptible in process context

Interrupt handlers are not preemptible in interrupt context

Interrupt handlers can take as much time they need in interrupt context