linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
To: Michael Kerrisk
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [PATCH] proc.5: Add info about /proc/[pid]/map_files directory
Date: Mon, 18 Feb 2013 20:50:59 +0400	[thread overview]
Message-ID: <51225BF3.7080602@parallels.com> (raw)

It was added into Linux v3.3 and provides info about files being mmap-ed in
a way _very_ similar to how /proc/[pid]/fd works. Thus I thought that the
best place for the map_files' doc is where where the fd's doc is.

Signed-off-by: Pavel Emelyanov <xemul-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>

---

diff --git a/man5/proc.5 b/man5/proc.5
index 30ca3a9..1226747 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -285,6 +285,23 @@ Thus the example command above could be written as:
 .RB "$" " foobar \-i /dev/stdin \-o /dev/stdout ..."
 .fi
 .in
+.TP
+.IR /proc/[pid]/map_files/ " (since kernel 3.3)
+This subdirectory contains entries corresponding to memory mapped
+files (see
+.BR mmap (2)).
+Entries are named by memory region start and end pair,
+and are symbolic links to the corresponding files.
+
+Although these entries are present for memory regions that were
+mapped with 
+.BR MAP_FILE
+flag, the way anonymous shared memory (regions created with
+.B MAP_ANON | MAP_SHARED
+flags)
+is implemented in Linux
+makes such regions also appear on this directory. In that case
+the target file would be the /dev/zero one.
 .\" FIXME Describe /proc/[pid]/loginuid
 .\"       Added in 2.6.11; updating requires CAP_AUDIT_CONTROL
 .\"       CONFIG_AUDITSYSCALL
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2013-02-18 16:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 16:50 Pavel Emelyanov [this message]
     [not found] ` <51225BF3.7080602-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-02-28 14:20   ` [PATCH] proc.5: Add info about /proc/[pid]/map_files directory Michael Kerrisk (man-pages)
     [not found]     ` <CAKgNAki5SQu8UffqN_s6-1=nATPJaf+KSAPNkGzCPDyyRSupNw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-16  6:02       ` Michael Kerrisk (man-pages)
     [not found]         ` <CAKgNAkigq6FW2oTG+JQBbpzEiK63K7WNZTyY2XN-huV4C78TOw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-16 17:19           ` Pavel Emelyanov

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=51225BF3.7080602@parallels.com \
    --to=xemul-bzqdu9zft3wakbo8gow8eq@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).