From: "Mike Black" <mblack@csihq.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Re: 2.4.7: wtf is "ksoftirqd_CPU0"
Date: Sun, 22 Jul 2001 06:24:06 -0400 [thread overview]
Message-ID: <009601c11298$70a3da80$b6562341@cfl.rr.com> (raw)
In-Reply-To: <000f01c111ff$73602ce0$c20e9c3e@host1> <3B59AFF7.8061645B@mandrakesoft.com> <01072201370202.02679@starship> <20010721165346.U3889@opus.bloom.county>
Actually -- is it possible (or desirable) to make ALL kernel daemons begin
with say "_" or some other special character to distinguish them from
userland threads? The "k......d" paradigm is OK but not very distinctive.
That way you have a simple line in the kernel docs that says "Any process
with a leading _ is a kernel process and should NEVER be killed or otherwise
messed with except as noted elsewhere in the docs".
Also would make it easy for things like ps, top and other process-aware
things to have a really simple "show kernel processes only" option.
----- Original Message -----
From: "Tom Rini" <trini@kernel.crashing.org>
To: "Daniel Phillips" <phillips@bonn-fries.net>
Cc: "peter k." <spam-goes-to-dev-null@gmx.net>;
<linux-kernel@vger.kernel.org>
Sent: Saturday, July 21, 2001 7:53 PM
Subject: [OT] Re: 2.4.7: wtf is "ksoftirqd_CPU0"
> On Sun, Jul 22, 2001 at 01:37:02AM +0200, Daniel Phillips wrote:
> > On Saturday 21 July 2001 18:38, Jeff Garzik wrote:
> > > "peter k." wrote:
> > > > i just installed 2.4.7, now a new process called "ksoftirqd_CPU0"
> > > > is started automatically when booting (by the kernel obviously)?
> > > > why? what does it do? i didnt find any useful information on it in
> > > > linuxdoc / linux-kernel archives
> > >
> > > it is used internally, ignore it.
> >
> > It's pretty hard to ignore a process with a name that ugly ;-)
> >
> > How about just ksoft0 ? Or kirq0?
>
> Now this is just getting silly. It follows the same convention the
> 6-8 other k* daemons follow. Would you want kswpd? kupd? kreclmd?
Probably
> not.
>
> --
> Tom Rini (TR1265)
> http://gate.crashing.org/~trini/
> -
> 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:[~2001-07-22 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-21 16:08 2.4.7: wtf is "ksoftirqd_CPU0" peter k.
2001-07-21 16:15 ` peter k.
2001-07-21 16:38 ` Jeff Garzik
2001-07-21 23:37 ` Daniel Phillips
2001-07-21 23:53 ` [OT] " Tom Rini
2001-07-22 10:24 ` Mike Black [this message]
2001-07-22 15:13 ` Andreas Schwab
2001-07-22 16:42 ` Horst von Brand
2001-07-23 14:14 ` Daniel Phillips
2001-07-22 0:23 ` Horst von Brand
2001-07-22 9:28 ` P.A.M. van Dam
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='009601c11298$70a3da80$b6562341@cfl.rr.com' \
--to=mblack@csihq.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