docs/vm: trivial fixes to several spelling mistakes
Fix several spelling mistakes in vm documentation. Signed-off-by: Colin Ian King <colin.king@canonical.com> Link: https://lore.kernel.org/r/20201022142653.254429-1-colin.king@canonical.com Signed-off-by: Jonathan Corbet <corbet@lwn.net>
This commit is contained in:
parent
030f066f67
commit
94ebdd28fc
@ -89,7 +89,7 @@ they are write protected for COW (other case of B apply too).
|
|||||||
|
|
||||||
So here because at time N+2 the clear page table entry was not pair with a
|
So here because at time N+2 the clear page table entry was not pair with a
|
||||||
notification to invalidate the secondary TLB, the device see the new value for
|
notification to invalidate the secondary TLB, the device see the new value for
|
||||||
addrB before seing the new value for addrA. This break total memory ordering
|
addrB before seeing the new value for addrA. This break total memory ordering
|
||||||
for the device.
|
for the device.
|
||||||
|
|
||||||
When changing a pte to write protect or to point to a new write protected page
|
When changing a pte to write protect or to point to a new write protected page
|
||||||
|
@ -99,7 +99,7 @@ Steps:
|
|||||||
2. Ensure that writeback is complete.
|
2. Ensure that writeback is complete.
|
||||||
|
|
||||||
3. Lock the new page that we want to move to. It is locked so that accesses to
|
3. Lock the new page that we want to move to. It is locked so that accesses to
|
||||||
this (not yet uptodate) page immediately block while the move is in progress.
|
this (not yet up-to-date) page immediately block while the move is in progress.
|
||||||
|
|
||||||
4. All the page table references to the page are converted to migration
|
4. All the page table references to the page are converted to migration
|
||||||
entries. This decreases the mapcount of a page. If the resulting
|
entries. This decreases the mapcount of a page. If the resulting
|
||||||
|
@ -18,7 +18,7 @@ Although we already have tracepoint for tracing page allocation/free,
|
|||||||
using it for analyzing who allocate each page is rather complex. We need
|
using it for analyzing who allocate each page is rather complex. We need
|
||||||
to enlarge the trace buffer for preventing overlapping until userspace
|
to enlarge the trace buffer for preventing overlapping until userspace
|
||||||
program launched. And, launched program continually dump out the trace
|
program launched. And, launched program continually dump out the trace
|
||||||
buffer for later analysis and it would change system behviour with more
|
buffer for later analysis and it would change system behaviour with more
|
||||||
possibility rather than just keeping it in memory, so bad for debugging.
|
possibility rather than just keeping it in memory, so bad for debugging.
|
||||||
|
|
||||||
page owner can also be used for various purposes. For example, accurate
|
page owner can also be used for various purposes. For example, accurate
|
||||||
|
@ -378,7 +378,7 @@ c) Execute ``slabinfo-gnuplot.sh`` in '-t' mode, passing all of the
|
|||||||
can go unnoticed. To deal with that, ``slabinfo-gnuplot.sh`` has two
|
can go unnoticed. To deal with that, ``slabinfo-gnuplot.sh`` has two
|
||||||
options to 'zoom-in'/'zoom-out':
|
options to 'zoom-in'/'zoom-out':
|
||||||
|
|
||||||
a) ``-s %d,%d`` -- overwrites the default image width and heigh
|
a) ``-s %d,%d`` -- overwrites the default image width and height
|
||||||
b) ``-r %d,%d`` -- specifies a range of samples to use (for example,
|
b) ``-r %d,%d`` -- specifies a range of samples to use (for example,
|
||||||
in ``slabinfo -X >> FOO_STATS; sleep 1;`` case, using a ``-r
|
in ``slabinfo -X >> FOO_STATS; sleep 1;`` case, using a ``-r
|
||||||
40,60`` range will plot only samples collected between 40th and
|
40,60`` range will plot only samples collected between 40th and
|
||||||
|
Loading…
Reference in New Issue
Block a user