[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+CK2bB2wz1c0kt0gegZ-MGnYBjbcdh3H-qo15R-egqt8pvquA@mail.gmail.com>
Date: Sun, 6 Nov 2022 08:46:26 -0500
From: Pasha Tatashin <pasha.tatashin@...een.com>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: corbet@....net, akpm@...ux-foundation.org, hughd@...gle.com,
hannes@...xchg.org, david@...hat.com, vincent.whitchurch@...s.com,
seanjc@...gle.com, rppt@...nel.org, shy828301@...il.com,
paul.gortmaker@...driver.com, peterx@...hat.com, vbabka@...e.cz,
Liam.Howlett@...cle.com, ccross@...gle.com, willy@...radead.org,
arnd@...db.de, cgel.zte@...il.com, yuzhao@...gle.com,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-doc@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] mm: anonymous shared memory naming
On Sat, Nov 5, 2022 at 5:34 AM Bagas Sanjaya <bagasdotme@...il.com> wrote:
>
> 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".
Thanks will update.
>
> > @@ -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.
Great, thank you.
Pasha
>
> --
> An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists