diff options
| author | Francis Galiegue | 2010-04-23 00:08:02 +0200 |
|---|---|---|
| committer | Jiri Kosina | 2010-04-23 02:09:52 +0200 |
| commit | a33f32244d8550da8b4a26e277ce07d5c6d158b5 (patch) | |
| tree | 2b24b891e48ae791446fef6d1b9e520190c03c62 /Documentation/cachetlb.txt | |
| parent | Merge branch 'master' into for-next (diff) | |
| download | kernel-qcow2-linux-a33f32244d8550da8b4a26e277ce07d5c6d158b5.tar.gz kernel-qcow2-linux-a33f32244d8550da8b4a26e277ce07d5c6d158b5.tar.xz kernel-qcow2-linux-a33f32244d8550da8b4a26e277ce07d5c6d158b5.zip | |
Documentation/: it's -> its where appropriate
Fix obvious cases of "it's" being used when "its" was meant.
Signed-off-by: Francis Galiegue <fgaliegue@gmail.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/cachetlb.txt')
| -rw-r--r-- | Documentation/cachetlb.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/cachetlb.txt b/Documentation/cachetlb.txt index 2b5f823abd03..9164ae3b83bc 100644 --- a/Documentation/cachetlb.txt +++ b/Documentation/cachetlb.txt @@ -5,7 +5,7 @@ This document describes the cache/tlb flushing interfaces called by the Linux VM subsystem. It enumerates over each interface, -describes it's intended purpose, and what side effect is expected +describes its intended purpose, and what side effect is expected after the interface is invoked. The side effects described below are stated for a uniprocessor @@ -231,7 +231,7 @@ require a whole different set of interfaces to handle properly. The biggest problem is that of virtual aliasing in the data cache of a processor. -Is your port susceptible to virtual aliasing in it's D-cache? +Is your port susceptible to virtual aliasing in its D-cache? Well, if your D-cache is virtually indexed, is larger in size than PAGE_SIZE, and does not prevent multiple cache lines for the same physical address from existing at once, you have this problem. @@ -249,7 +249,7 @@ one way to solve this (in particular SPARC_FLAG_MMAPSHARED). Next, you have to solve the D-cache aliasing issue for all other cases. Please keep in mind that fact that, for a given page mapped into some user address space, there is always at least one more -mapping, that of the kernel in it's linear mapping starting at +mapping, that of the kernel in its linear mapping starting at PAGE_OFFSET. So immediately, once the first user maps a given physical page into its address space, by implication the D-cache aliasing problem has the potential to exist since the kernel already |