From: Randy Dunlap <rdunlap@infradead.org>
To: alexlzhu@fb.com, corbet@lwn.net, bobwxc@email.cn,
rppt@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Kernel-team@fb.com
Subject: Re: [PATCH v2] docs: admin-guide/mm: Improve grammar on MM concepts documentation
Date: Tue, 16 Aug 2022 15:36:32 -0700 [thread overview]
Message-ID: <299a0328-9d93-74ca-a2b2-114dfd896056@infradead.org> (raw)
In-Reply-To: <20220816022621.253778-1-alexlzhu@fb.com>
Hi--
On 8/15/22 19:26, alexlzhu@fb.com wrote:
> From: Alexander Zhu <alexlzhu@fb.com>
>
> Improve grammar on MM concepts documentation.
>
> Signed-off-by: Alexander Zhu <alexlzhu@fb.com>
> ---
> Documentation/admin-guide/mm/concepts.rst | 138 +++++++++++-----------
> 1 file changed, 68 insertions(+), 70 deletions(-)
>
> diff --git a/Documentation/admin-guide/mm/concepts.rst b/Documentation/admin-guide/mm/concepts.rst
> index c79f1e336222..c471f80b7a38 100644
> --- a/Documentation/admin-guide/mm/concepts.rst
> +++ b/Documentation/admin-guide/mm/concepts.rst
[snip]
> -Depending on the page usage it is treated differently by the Linux
> -memory management. The pages that can be freed at any time, either
> -because they cache the data available elsewhere, for instance, on a
> -hard disk, or because they can be swapped out, again, to the hard
> +Depending on page usage it is treated differently by the Linux
> +memory management subsystem. Pages that can be freed at any time,
> +either because they cache the data available elsewhere
> +(ie on a hard disk) or because they can be swapped out to the hard
(i.e., on a hard disk)
> disk, are called `reclaimable`. The most notable categories of the
> reclaimable pages are page cache and anonymous memory.
>
[snip]
>
> Compaction
> ==========
>
> -As the system runs, tasks allocate and free the memory and it becomes
> +As the system runs, tasks will allocate and free memory. Memory thus becomes
Addition of "will" is not needed.
> fragmented. Although with virtual memory it is possible to present
> -scattered physical pages as virtually contiguous range, sometimes it is
> +scattered physical pages as a virtually contiguous range, sometimes it is
> necessary to allocate large physically contiguous memory areas. Such
> need may arise, for instance, when a device driver requires a large
> buffer for DMA, or when THP allocates a huge page. Memory `compaction`
Thanks.
--
~Randy
prev parent reply other threads:[~2022-08-16 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 2:26 [PATCH v2] docs: admin-guide/mm: Improve grammar on MM concepts documentation alexlzhu
2022-08-16 11:18 ` Wu XiangCheng
2022-08-16 22:36 ` Randy Dunlap [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=299a0328-9d93-74ca-a2b2-114dfd896056@infradead.org \
--to=rdunlap@infradead.org \
--cc=Kernel-team@fb.com \
--cc=alexlzhu@fb.com \
--cc=bobwxc@email.cn \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox