All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hua Zhong" <hzhong@gmail.com>
To: "'Jan Engelhardt'" <jengelh@linux01.gwdg.de>,
	"'Mikado'" <mikado4vn@gmail.com>
Cc: "'linux-os \(Dick Johnson\)'" <linux-os@analogic.com>,
	"'Linux kernel'" <linux-kernel@vger.kernel.org>
Subject: RE: Which process is associated with process ID 0 (swapper)
Date: Thu, 20 Apr 2006 15:15:15 -0700	[thread overview]
Message-ID: <004801c664c7$e80acfd0$853d010a@nuitysystems.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0604210007140.28841@yvahk01.tjqt.qr>

> >Linux really has swapper process ;)
> >
> To be precise, it has more than one.
> 
> When you hit an OOPS, the trace [1] might show:
> "Pid: 0, comm: swapper Not tainted 2.6.11.6"
> 
> Plus you see one of these per CPU [ps aufwwx]:
> root       106  0.0  0.0      0     0 ?        S    Apr20   
> 0:04 [kswapd0]
> 
> So, a question to the public: what swapper swaps, and what's 
> swapper(as in pid 0) in oops, if there's no PID 0?

Swapper is the idle process, which swaps nothing. Its name is historic and it doesn't appear in /proc because for_each_process()
skips it.

Kswapd is totally different.


  reply	other threads:[~2006-04-20 22:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 14:58 Which process is associated with process ID 0 (swapper) Mikado
2006-04-20 15:30 ` linux-os (Dick Johnson)
2006-04-20 15:48   ` Mike Galbraith
2006-04-20 16:04   ` Mikado
2006-04-20 16:39     ` Joshua Hudson
2006-04-20 22:10     ` Jan Engelhardt
2006-04-20 22:15       ` Hua Zhong [this message]
2006-04-20 22:19         ` Jan Engelhardt
2006-04-20 23:12           ` Mikado
2006-04-21 12:46             ` Jan Engelhardt
2006-04-20 23:19       ` Mikado
2006-04-20 23:35       ` Mikado
2006-04-21  0:37         ` Patrick McHardy
2006-04-21  1:33           ` Mikado
2006-04-21  3:16             ` Bernd Eckenfels
2006-04-21 12:48           ` Jan Engelhardt
2006-04-21 12:52             ` Jan Engelhardt
2006-04-21 15:21               ` Mikado
2006-04-20 22:06   ` Jan Engelhardt

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='004801c664c7$e80acfd0$853d010a@nuitysystems.com' \
    --to=hzhong@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=mikado4vn@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 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.