Kernel Recipes 2016 - Who needs a Real-Time Operating System (Not You!) - Steven Rostedt
Вставка
- Опубліковано 27 кві 2024
- A Real-Time Operating System (RTOS) is used for mission critical projects that require a deterministic response time for external stimuli. Many times project managers request an RTOS even though they don’t fully understand what exactly an RTOS gives them. And many times, a normal OS would do just fine, and perhaps even better, as an RTOS sacrifices throughput for determinism.
This talk will discuss exactly what an RTOS is and what it is good for. What types of requirements that require having an RTOS will be explained, as well as requirements where not having on RTOS would be more appropriate. You do not need to be a programmer to enjoy this talk. It will be discussed at a very high level but still contain enough information for a seasoned developer to get something out of it too.
Steven Rostedt, Red Hat - Наука та технологія
I worked with Hewlett Packard's RTE HP1000 in the 1980s. Your presentation, definition wise, is nearly identical to mine - happy to see the issues are current :-)
Excellent talk, Steve!
quite technical but thank you for working on RT system... what is really needed in audio production will be a dedicated "Linux" working like "direct to disk" (what I am dreaming about since so long...)
Too bad no one laughed at the DOS gag at 2:53 … well I did. *lol*
What if low priority task crash after inheriting priority?
please help me how to do rtpatch or any link ,videos
Real time is making its way into mainline now 😁
Anyone got the URL for the "next talk" he kept mentioning ?
ua-cam.com/video/w3yT8zJe0Uw/v-deo.html
Horse Manure! If I hit a button and it lags too much before I see the letter I typed, you've missed a deadline!
No you haven't. A laggy keyboard performs the same function as a responsive keyboard. A bad user experience isn't the same thing as missing a real-time deadline.
If I'm trading on a financial exchange and my order is executed late, my transaction might return invalidated. It's not just that the response is "laggy," but that what actually happened changed because I missed a time constraint.
"Pardon my french" :)
Great talk!
A bit more details about the Mars Rover Pathfinder priority inversion bug: www.cs.cornell.edu/courses/cs614/1999sp/papers/pathfinder.html. Seems like the solution actually was to turn on priority inheritance for the mutex.
still got some hp 1000 at work working ....
Nobody ever needed more than 640k, either.