[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1461566229-4717-13-git-send-email-eric@engestrom.ch>
Date: Mon, 25 Apr 2016 07:37:05 +0100
From: Eric Engestrom <eric@...estrom.ch>
To: linux-kernel@...r.kernel.org
Cc: Eric Engestrom <eric@...estrom.ch>,
Jonathan Corbet <corbet@....net>,
Andrew Morton <akpm@...ux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Rik van Riel <riel@...hat.com>,
Vlastimil Babka <vbabka@...e.cz>,
Ebru Akagunduz <ebru.akagunduz@...il.com>,
Mel Gorman <mgorman@...hsingularity.net>,
linux-doc@...r.kernel.org
Subject: [PATCH 39/41] Documentation: vm: fix spelling mistakes
Signed-off-by: Eric Engestrom <eric@...estrom.ch>
---
Documentation/vm/transhuge.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/vm/transhuge.txt b/Documentation/vm/transhuge.txt
index d9cb65c..2f383f6 100644
--- a/Documentation/vm/transhuge.txt
+++ b/Documentation/vm/transhuge.txt
@@ -340,7 +340,7 @@ unaffected. libhugetlbfs will also work fine as usual.
== Graceful fallback ==
-Code walking pagetables but unware about huge pmds can simply call
+Code walking pagetables but unaware about huge pmds can simply call
split_huge_pmd(vma, pmd, addr) where the pmd is the one returned by
pmd_offset. It's trivial to make the code transparent hugepage aware
by just grepping for "pmd_offset" and adding split_huge_pmd where
@@ -414,7 +414,7 @@ tracking. The alternative is alter ->_mapcount in all subpages on each
map/unmap of the whole compound page.
We set PG_double_map when a PMD of the page got split for the first time,
-but still have PMD mapping. The addtional references go away with last
+but still have PMD mapping. The additional references go away with last
compound_mapcount.
split_huge_page internally has to distribute the refcounts in the head
@@ -433,7 +433,7 @@ We safe against physical memory scanners too: the only legitimate way
scanner can get reference to a page is get_page_unless_zero().
All tail pages has zero ->_count until atomic_add(). It prevent scanner
-from geting reference to tail page up to the point. After the atomic_add()
+from getting reference to tail page up to the point. After the atomic_add()
we don't care about ->_count value. We already known how many references
with should uncharge from head page.
--
2.8.0
Powered by blists - more mailing lists