On Thu, 28 Apr 2016 07:46:07 -0600 Jonathan Corbet <[hidden email]> wrote:
> On Thu, 28 Apr 2016 07:31:43 -0600
> Jonathan Corbet <[hidden email]> wrote:
> > On Mon, 25 Apr 2016 07:37:05 +0100
> > Eric Engestrom <[hidden email]> wrote:
> > > Documentation/vm/transhuge.txt | 6 +++---
> > > 1 file changed, 3 insertions(+), 3 deletions(-)
> > Applied to the docs tree, thanks.
> Actually, I've just unapplied this one; it conflicts against changes in
> Andrew's tree and, thus, linux-next. Andrew, maybe you'd like to take it
> on top of what you have now?
That Documentation/vm/transhuge.txt paragraph isn't in great shape so
I gave it some extra help.
diff -puN Documentation/vm/transhuge.txt~documentation-vm-fix-spelling-mistakes Documentation/vm/transhuge.txt
@@ -340,7 +340,7 @@ unaffected. libhugetlbfs will also work
== 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 ->_ma
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
split_huge_page internally has to distribute the refcounts in the head
@@ -432,10 +432,10 @@ page->_mapcount.
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 ->_refcount until atomic_add(). It prevent scanner
-from geting reference to tail page up to the point. After the atomic_add()
-we don't care about ->_refcount value. We already known how many references
-with should uncharge from head page.
+All tail pages have zero ->_refcount until atomic_add(). This prevents the
+scanner from getting a reference to the tail page up to that point. After the
+atomic_add() we don't care about the ->_refcount value. We already known how
+many references should be uncharged from the head page.
For head page get_page_unless_zero() will succeed and we don't mind. It's
clear where reference should go after split: it will stay on head page.
> Signed-off-by: Eric Engestrom <[hidden email]>
> Documentation/fb/udlfb.txt | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> diff --git a/Documentation/fb/udlfb.txt b/Documentation/fb/udlfb.txt
> index 57d2f29..c985cb6 100644
> --- a/Documentation/fb/udlfb.txt
> +++ b/Documentation/fb/udlfb.txt
> @@ -9,7 +9,7 @@ pairing that with a hardware framebuffer (16MB) on the other end of the
> USB wire. That hardware framebuffer is able to drive the VGA, DVI, or HDMI
> monitor with no CPU involvement until a pixel has to change.
> -The CPU or other local resource does all the rendering; optinally compares the
> +The CPU or other local resource does all the rendering; optionally compares the
> result with a local shadow of the remote hardware framebuffer to identify
> the minimal set of pixels that have changed; and compresses and sends those
> pixels line-by-line via USB bulk transfers.
> @@ -66,10 +66,10 @@ means that from a hardware and fbdev software perspective, everything is good.
> At that point, a /dev/fb? interface will be present for user-mode applications
> to open and begin writing to the framebuffer of the DisplayLink device using
> standard fbdev calls. Note that if mmap() is used, by default the user mode
> -application must send down damage notifcations to trigger repaints of the
> +application must send down damage notifications to trigger repaints of the
> changed regions. Alternatively, udlfb can be recompiled with experimental
> defio support enabled, to support a page-fault based detection mechanism
> -that can work without explicit notifcation.
> +that can work without explicit notification.
> The most common client of udlfb is xf86-video-displaylink or a modified
> xf86-video-fbdev X server. These servers have no real DisplayLink specific