All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-kernel@vger.kernel.org
Cc: Luis Garces-Erice <lge@ieee.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Subject: [PATCH 5/6] docs: better explanation of procs_running
Date: Sun, 06 Dec 2009 18:30:44 -0800	[thread overview]
Message-ID: <12601530441257@xenotime.net> (raw)
In-Reply-To: <12601530442994@xenotime.net>

From:	Luis Garces-Erice <lge@ieee.org>
Subject: Doc: better explanation of procs_running

the description in Documentation/filesystems/proc.txt of the
procs_running entry in /proc/stat is confusing (according to that
description, it looks as if procs_running could only be a number
between 0 and the number of CPUs).

Changed it to a more accurate description in the patch attached.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 Documentation/filesystems/proc.txt |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

--- lnx-2632-rc6.orig/Documentation/filesystems/proc.txt
+++ lnx-2632-rc6/Documentation/filesystems/proc.txt
@@ -1088,8 +1088,8 @@ The "processes" line gives the number  o
 includes (but  is not limited  to) those  created by  calls to the  fork() and
 clone() system calls.
 
-The  "procs_running" line gives the  number of processes  currently running on
-CPUs.
+The "procs_running" line gives the total number of threads that are
+running or ready to run (i.e., the total number of runnable threads).
 
 The   "procs_blocked" line gives  the  number of  processes currently blocked,
 waiting for I/O to complete.


-- 


  reply	other threads:[~2009-12-07  3:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  2:30 [PATCH 1/6 for 2.6.33] docs: use KERN_WARNING, not KERN_WARN Randy Dunlap
2009-12-07  2:30 ` Randy Dunlap [this message]
2009-12-07  2:30 ` [PATCH 6/6] docs: use misc-devices/ dir for drivers Randy Dunlap
2009-12-07  2:30 ` [PATCH 3/6] docs: fix signal_pending argument Randy Dunlap
2009-12-07  2:30 ` [PATCH 2/6] docs: use DMA_BIT_MASK instead of inline constant Randy Dunlap
2009-12-07  4:09 ` [PATCH 1/6 for 2.6.33] docs: use KERN_WARNING, not KERN_WARN Joe Perches

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=12601530441257@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=lge@ieee.org \
    --cc=linux-kernel@vger.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 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.