From: Andreas Schwab <schwab@suse.de>
To: "Mike Black" <mblack@csihq.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Re: 2.4.7: wtf is "ksoftirqd_CPU0"
Date: 22 Jul 2001 17:13:54 +0200 [thread overview]
Message-ID: <je3d7pxah9.fsf@sykes.suse.de> (raw)
In-Reply-To: <000f01c111ff$73602ce0$c20e9c3e@host1> <3B59AFF7.8061645B@mandrakesoft.com> <01072201370202.02679@starship> <20010721165346.U3889@opus.bloom.county> <009601c11298$70a3da80$b6562341@cfl.rr.com>
In-Reply-To: <009601c11298$70a3da80$b6562341@cfl.rr.com> ("Mike Black"'s message of "Sun, 22 Jul 2001 06:24:06 -0400")
"Mike Black" <mblack@csihq.com> writes:
|> 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.
Kernel threads can easily be identified by having a zero virtual size.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
next prev parent reply other threads:[~2001-07-22 15:14 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
2001-07-22 15:13 ` Andreas Schwab [this message]
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=je3d7pxah9.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mblack@csihq.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