All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marko Myllynen <myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: /proc/{diskstats,schedstat,vmstat} documentation
Date: Wed, 13 May 2015 12:50:23 +0300	[thread overview]
Message-ID: <55531E5F.2090803@redhat.com> (raw)

Hi Michael,

it seems that /proc/vmstat is undocumented in proc(5), is it just
because nobody has written the documentation yet or are some files
considered out of scope for proc(5)? Other such "interesting" file which
would be nice to have documented in-line is IMHO /proc/diskstats.

FWIW, for /proc/vmstat first search hit is
http://www.linuxinsight.com/proc_vmstat.html which looks decent.

I also see that /proc/schedstat and /proc/<pid>/schedstat are missing,
some information about them can be found at
http://eaglet.rain.com/rick/linux/schedstat/v15/format-15.html and
https://www.kernel.org/doc/Documentation/scheduler/sched-stats.txt.

Lastly, /proc/<pid>/{loginuid,sessionid} are missing.

PS. Yes, I think I try to provide patches at least for a couple of these
cases if time permits.

Thanks,

-- 
Marko Myllynen
--
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:[~2015-05-13  9:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  9:50 Marko Myllynen [this message]
     [not found] ` <55531E5F.2090803-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-13 13:03   ` /proc/{diskstats,schedstat,vmstat} documentation Michael Kerrisk (man-pages)
     [not found]     ` <55534B8B.8010400-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-05-13 15:08       ` Michael Kerrisk (man-pages)

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=55531E5F.2090803@redhat.com \
    --to=myllynen-h+wxahxf7alqt0dzr+alfa@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 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.