summaryrefslogtreecommitdiff
path: root/Documentation/x86/tlb.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/x86/tlb.txt')
-rw-r--r--Documentation/x86/tlb.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/x86/tlb.txt b/Documentation/x86/tlb.txt
index 39d172326..6a0607b99 100644
--- a/Documentation/x86/tlb.txt
+++ b/Documentation/x86/tlb.txt
@@ -5,7 +5,7 @@ memory, it has two choices:
from areas other than the one we are trying to flush will be
destroyed and must be refilled later, at some cost.
2. Use the invlpg instruction to invalidate a single page at a
- time. This could potentialy cost many more instructions, but
+ time. This could potentially cost many more instructions, but
it is a much more precise operation, causing no collateral
damage to other TLB entries.
@@ -19,7 +19,7 @@ Which method to do depends on a few things:
work.
3. The size of the TLB. The larger the TLB, the more collateral
damage we do with a full flush. So, the larger the TLB, the
- more attrative an individual flush looks. Data and
+ more attractive an individual flush looks. Data and
instructions have separate TLBs, as do different page sizes.
4. The microarchitecture. The TLB has become a multi-level
cache on modern CPUs, and the global flushes have become more