From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: corbet@lwn.net, akpm@linux-foundation.org, hughd@google.com,
hannes@cmpxchg.org, david@redhat.com,
vincent.whitchurch@axis.com, seanjc@google.com, rppt@kernel.org,
shy828301@gmail.com, paul.gortmaker@windriver.com,
peterx@redhat.com, vbabka@suse.cz, Liam.Howlett@oracle.com,
ccross@google.com, willy@infradead.org, arnd@arndb.de,
cgel.zte@gmail.com, yuzhao@google.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: anonymous shared memory naming
Date: Sat, 5 Nov 2022 16:34:05 +0700 [thread overview]
Message-ID: <Y2YuDfQbAwtLRLq4@debian.me> (raw)
In-Reply-To: <20221105025342.3130038-1-pasha.tatashin@soleen.com>
[-- Attachment #1: Type: text/plain, Size: 3174 bytes --]
On Sat, Nov 05, 2022 at 02:53:42AM +0000, Pasha Tatashin wrote:
> Since:
> commit 9a10064f5625 ("mm: add a field to store names for private anonymous
> memory")
>
> We can set names for private anonymous memory but not for shared
> anonymous memory. However, naming shared anonymous memory just as
> useful for tracking purposes.
>
Who are "we"?
Instead, say "Since commit <commit>, name for private anonymous memory,
but not shared anonymous, can be set".
> @@ -431,8 +431,10 @@ is not associated with a file:
> [stack] the stack of the main process
> [vdso] the "virtual dynamic shared object",
> the kernel system call handler
> - [anon:<name>] an anonymous mapping that has been
> + [anon:<name>] a private anonymous mapping that has been
> named by userspace
> + path [anon_shmem:<name>] an anonymous shared memory mapping that has
> + been named by userspace
> ============= ====================================
>
The table above triggers Sphinx warning:
Documentation/filesystems/proc.rst:436: WARNING: Malformed table.
Text in column margin in table line 8.
============= ====================================
[heap] the heap of the program
[stack] the stack of the main process
[vdso] the "virtual dynamic shared object",
the kernel system call handler
[anon:<name>] a private anonymous mapping that has been
named by userspace
path [anon_shmem:<name>] an anonymous shared memory mapping that has
been named by userspace
============= ====================================
I have applied the fixup:
---- >8 ----
diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
index 8f1e68460da5cd..3f17b4ef307fe4 100644
--- a/Documentation/filesystems/proc.rst
+++ b/Documentation/filesystems/proc.rst
@@ -426,7 +426,7 @@ with the memory region, as the case would be with BSS (uninitialized data).
The "pathname" shows the name associated file for this mapping. If the mapping
is not associated with a file:
- ============= ====================================
+ ======================== ===========================================
[heap] the heap of the program
[stack] the stack of the main process
[vdso] the "virtual dynamic shared object",
@@ -435,7 +435,7 @@ is not associated with a file:
named by userspace
path [anon_shmem:<name>] an anonymous shared memory mapping that has
been named by userspace
- ============= ====================================
+ ======================== ===========================================
or if empty, the mapping is anonymous.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-11-05 9:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 2:53 [PATCH] mm: anonymous shared memory naming Pasha Tatashin
2022-11-05 8:27 ` kernel test robot
2022-11-05 9:34 ` Bagas Sanjaya [this message]
2022-11-06 13:46 ` Pasha Tatashin
2022-11-06 13:33 ` Kirill A. Shutemov
2022-11-06 13:45 ` Pasha Tatashin
2022-11-06 16:52 ` Kirill A. Shutemov
2022-11-07 15:59 ` Pasha Tatashin
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=Y2YuDfQbAwtLRLq4@debian.me \
--to=bagasdotme@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ccross@google.com \
--cc=cgel.zte@gmail.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=paul.gortmaker@windriver.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=shy828301@gmail.com \
--cc=vbabka@suse.cz \
--cc=vincent.whitchurch@axis.com \
--cc=willy@infradead.org \
--cc=yuzhao@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.