public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@cfl.rr.com>
To: vamsi krishna <vamsi.krishnak@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Process states inside the linux kernel. [Especially about the STATE D]
Date: Mon, 20 Feb 2006 17:34:58 -0500	[thread overview]
Message-ID: <43FA4412.6010303@cfl.rr.com> (raw)
In-Reply-To: <3faf05680602201419v3a6172a1j80e4210dde4c54cf@mail.gmail.com>

vamsi krishna wrote:
> Hello All,
> 
>  I have been debugging a program which takes huge memory around 12Gb
> (On a 64-bit machine). I was trying to monitor the VmSize and RSS
> sizes using top command for this process. I frequently see that the
> process STATUS changes its state from 'D' to 'R' most of the time its
> in the state 'D'.
> 
>  I looked at the manual it says D  uninterruptable sleep state (I have
> googled on this but could'nt find much information about this stage).
> As far as my text book knowledge, the process is either 1). Running 
> 'R'  2.) Ready 'Re' 3.) Wait (for I/O) W .
> 
>  So what is 'uninterruptable sleep state' D ? when does the process is
> put in this state?
> 
>  Can someone releate me the states cycle of the process in linux kernel.
> 
>  Really appreciate your time and effort.
> 

It is called D because originally it stood for Disk, and was used for 
when the process was blocked waiting to be swapped back in from the 
disk. These days it is still mostly used for when the process is blocked 
either handling a page fault or in a system call that does blocking disk 
IO.



      reply	other threads:[~2006-02-20 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 22:19 Process states inside the linux kernel. [Especially about the STATE D] vamsi krishna
2006-02-20 22:34 ` Phillip Susi [this message]

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=43FA4412.6010303@cfl.rr.com \
    --to=psusi@cfl.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vamsi.krishnak@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox