From: "Hua Zhong" <hzhong@gmail.com>
To: "'Joshua Hudson'" <joshudson@gmail.com>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Rename "swapper" to "idle"
Date: Thu, 20 Apr 2006 22:19:57 -0700 [thread overview]
Message-ID: <000301c66503$3bbd8060$0200a8c0@nuitysystems.com> (raw)
In-Reply-To: <bda6d13a0604202118t51709a70g1f2402efb8ecbfe@mail.gmail.com>
> On 4/20/06, Bernd Eckenfels <be-news06@lina.inka.de> wrote:
> > Hua Zhong <hzhong@gmail.com> wrote:
> > > This patch renames the "swapper" process (pid 0) to a
> more appropriate name "idle". The name "swapper" is not
> obviously meaningful and confuses a lot of people (e.g., when
> seen in oops report).
> > > Patch not tested, but I guess it works. :-)
>
> As we saw in "Which process is associated with process ID 0
> (swapper)", pid 0 can actually do things, such as resend TCP
> packets. Methinks idle isn't the best name either.
Swapper does not do these things. It just happens to be "running" at that time (and it is always running if the system is idle).
IOW, it is indeed an "idle" process. In fact, all it does is cpu_idle().
> > on win the system idle process shows up in taskmanager so
> you can see
> > its cpu usage and ctx switches scheduled from it. We could
> avoid the
> > skipping in /proc, also?
> >
> > Gruss
> > Bernd
> Please, no!
>
> I already have to explain this mess about Windows. We
> shouldn't be implementing Microsoft's flaws. Why waist the a
> line of screen for top?
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to
> majordomo@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2006-04-21 5:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 23:15 [PATCH] Rename "swapper" to "idle" Hua Zhong
2006-04-21 0:17 ` Steven Rostedt
2006-04-21 0:35 ` Bernd Eckenfels
2006-04-21 4:18 ` Joshua Hudson
2006-04-21 5:19 ` Hua Zhong [this message]
2006-04-21 14:40 ` Mikado
2006-04-21 14:56 ` Michael Buesch
2006-04-21 15:08 ` Jan Engelhardt
2006-04-21 17:05 ` Steven Rostedt
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='000301c66503$3bbd8060$0200a8c0@nuitysystems.com' \
--to=hzhong@gmail.com \
--cc=joshudson@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox