Change bold code snippets to inline code blocks
This commit is contained in:
parent
f658bfbb40
commit
3c76d884ef
185 changed files with 1772 additions and 1772 deletions
4
11-02.md
4
11-02.md
|
|
@ -100,7 +100,7 @@ wait states hurt plenty—and the place they hurt most is instruction
|
|||
fetching.
|
||||
|
||||
Consider this: The 286 can store an immediate value to memory, as in
|
||||
**MOV [WordVar],0**, in just 3 cycles. However, that instruction is 6
|
||||
`MOV [WordVar],0`, in just 3 cycles. However, that instruction is 6
|
||||
bytes long. The 286 is capable of fetching 1 word every 2 cycles;
|
||||
however, the one-wait-state architecture of the AT stretches that to 3
|
||||
cycles. Consequently, nine cycles are needed to fetch the six
|
||||
|
|
@ -117,7 +117,7 @@ the above example: A 4-to-1 ratio of instruction fetch time to execution
|
|||
time is in a class with the best (or worst!) that's found on the 8088.
|
||||
|
||||
Let's check out the prefetch queue cycle-eater in action. Listing 11.1
|
||||
times **MOV [WordVar],0**. The Zen timer reports that on a
|
||||
times `MOV [WordVar],0`. The Zen timer reports that on a
|
||||
one-wait-state 10 MHz 286-based AT clone (the computer used for all
|
||||
tests in this chapter), Listing 11.1 runs in 1.27 µs per instruction.
|
||||
That's 12.7 cycles per instruction, just as we calculated. (That extra
|
||||
|
|
|
|||
Loading…
Reference in a new issue