2.4.7: wtf is "ksoftirqd_CPU0"

2.4.7: wtf is "ksoftirqd_CPU0"

[peter k.]

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

Re: 2.4.7: wtf is "ksoftirqd_CPU0"

[peter k.]

i knew that i forgot to say something: i was using 2.4.6 before and i never
saw that process with 2.4.6 or any other 2.4.x version


> 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

Re: 2.4.7: wtf is "ksoftirqd_CPU0"

[Jeff Garzik]

"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.

-- 
Jeff Garzik      | "I wouldn't be so judgemental
Building 1024    |  if you weren't such a sick freak."
MandrakeSoft     |             -- goats.com

Re: 2.4.7: wtf is "ksoftirqd_CPU0"

[Daniel Phillips]

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?

I don't see the sense of trying to encode a whole sentence into the 
process name.

(Peter, this handles softirqs in a more predictable way by allowing the 
scheduler to take care of any softirq that can't conveniently be 
executed immediately.  Among other benefits, this approach eliminated 
the need to check for and execute pending softirqs on exit from system 
calls.)

--
Daniel

[OT] Re: 2.4.7: wtf is "ksoftirqd_CPU0"

[Tom Rini]

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/

Re: [OT] Re: 2.4.7: wtf is "ksoftirqd_CPU0"

[Mike Black]

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/

Re: [OT] Re: 2.4.7: wtf is "ksoftirqd_CPU0"

[Andreas Schwab]

"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

Re: [OT] Re: 2.4.7: wtf is "ksoftirqd_CPU0"

[Horst von Brand]

"Mike Black" <mblack@csihq.com> said:
> 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".

It is rather easy to fake any process name.
-- 
Horst von Brand                             vonbrand@sleipnir.valparaiso.cl
Casilla 9G, Vin~a del Mar, Chile                               +56 32 672616

Re: [OT] Re: 2.4.7: wtf is "ksoftirqd_CPU0"

[Daniel Phillips]

On Sunday 22 July 2001 01:53, Tom Rini wrote:
> 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.

Err, wasn't I arguing *against* trying to encode whole sentences in the 
daemon names?  Personally, I have a similar distaste for naming 
strategies that involve leaving out the vowels.

And no, I don't really like kirq or ksoft very much either.

I'd like to see the following in my ps -A list:

  kupdate
  kflush
  kinterrupt

Something like that.  We don't need d's at the ends because we have k's 
at the beginnings, don't you think?  I can see the logic for appending 
numbers to per-processor daemons, but as for doing it even on UP 
kernels, it's not so obviously a good idea.

As far as 'naming conventions' for daemons go, they went out the window 
when kflushd became bdflush.

--
Daniel

Re: 2.4.7: wtf is "ksoftirqd_CPU0"

[Horst von Brand]

Jeff Garzik <jgarzik@mandrakesoft.com> said:
> "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.

I'd advise not to do so in general: It is a rather tempting name for
crackers to hide illegal activities.
-- 
Horst von Brand                             vonbrand@sleipnir.valparaiso.cl
Casilla 9G, Vin~a del Mar, Chile                               +56 32 672616

Re: 2.4.7: wtf is "ksoftirqd_CPU0"

[P.A.M. van Dam]

On Sat, Jul 21, 2001 at 08:23:36PM -0400, Horst von Brand wrote:
> Jeff Garzik <jgarzik@mandrakesoft.com> said:
> > "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.
> 
> I'd advise not to do so in general: It is a rather tempting name for
> crackers to hide illegal activities.

Kernel daemons/threads still use "reserved pids" (< 100 I believe) so it's
pretty to distinguish them. Ofcourse on 128-way SMP machine, things would
be rather difficult. 

Best regards,

	Pascal


> -- 
> Horst von Brand                             vonbrand@sleipnir.valparaiso.cl
> Casilla 9G, Vin~a del Mar, Chile                               +56 32 672616
> -
> 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/