You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
7I don't think it has nothing to do with the CPU at all, or even the interrupt controller, but running on a real-time OS or on bare metal without OS at all, and Windows is not a real-time OS. If you make a 8086 system that runs with code on ROM and data on SRAM, it would be a very real time system, as not even DRAM refresh would steal CPU cycles.– JustmeCommented Oct 16, 2020 at 18:25
-
30Real-time systems aren't about the latency - it just needs to be low enough. It's mostly about the predictability. The jitter in the latency, if you will. So controlling every aspect of execution so that timing predictions are accurate and consistent...– Brian HCommented Oct 16, 2020 at 18:40
-
9A 8086 to 80586 CPU isn't any more "modern" than a 68k CPU - they were contemporary.– tofroCommented Oct 16, 2020 at 19:42
-
4That Wikipedia article seems to mix up interrupt architecture and OS structure, The second is irrelevant, you don't use a non-real-time OS if you want real-time response. But the paragraph in question is about "using your home computer", so perhaps their self-imposed restriction is using it with the vendor-supplied OS.– daveCommented Oct 16, 2020 at 22:35
-
2I think "modern" doesn't belong in the question title. Nothing about the body of the question seems to relate to what I would call "modern" x86 (really x64 but that's just confusing) processors. For one thing, the PIC mentioned in the quotes has been superseded by a much more sophisticated system. For another, the clock speeds and parallel processing cores in a modern Intel compatible CPU means you can't really compare with a 68000 series architecture any more.– Todd WilcoxCommented Oct 17, 2020 at 3:51
|
Show 15 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. ms-dos), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you