this post was submitted on 30 May 2024
76 points (100.0% liked)
Linux
48157 readers
619 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I guess i am still skipping on how real time kernel address the pause? it just never pauses or it no longer needs to be paused?
as a side note, is this similar technology they use in high precision manufacturing?
Think of it like a club with a max capacity of 10 people, where some people have VIP cards. If a person with a VIP card wants to get into the club, the bouncer will kick out one of the people inside that doesn't have a VIP card to make space for them.
For a more technical explanation:
There are several processors on computers and each can be in use by 1 process at a time. Different processes can get different amounts of time based on their priority (called niceness in Linux) and they'll be removed from the processor once their time is up until their next share of time.
On a real-time kernel some processes are marked as real-time (certain range of niceness values, can't remember the exact range). If a process that is real-time says it needs some processor time, a process that isn't real-time that's currently running will be immediately ripped off the processor to make room for the real-time process.
Alright, this landed!
When hardware has data ready for a program it generates an interrupt that lets the OS know that there is data ready for an application. My understanding is that real-time OSs give high priority to interrupts so that they're processed quickly - usually within a fixed period of time (e.g. they may have a max time between interrupt and processing).
In those cases it may be more likely they use a micro-controller that doesn't run any OS at all - at least not a multi-tasking one. If you're just running a single program you don't need to worry about latency due to other applications running.