public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Jeff Garzik <jgarzik@mandrakesoft.com>,
	"peter k." <spam-goes-to-dev-null@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.7: wtf is "ksoftirqd_CPU0"
Date: Sun, 22 Jul 2001 01:37:02 +0200	[thread overview]
Message-ID: <01072201370202.02679@starship> (raw)
In-Reply-To: <000f01c111ff$73602ce0$c20e9c3e@host1> <3B59AFF7.8061645B@mandrakesoft.com>
In-Reply-To: <3B59AFF7.8061645B@mandrakesoft.com>

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

  reply	other threads:[~2001-07-21 23:32 UTC|newest]

Thread overview: 14+ 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 [this message]
2001-07-21 23:53     ` [OT] " Tom Rini
2001-07-22 10:24       ` Mike Black
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
     [not found] <NOEJJDACGOHCKNCOGFOMCECBCKAA.davids@webmaster.com>
2001-07-21 16:29 ` peter k.
2001-07-21 16:36   ` Arnaldo Carvalho de Melo
2001-07-21 17:15   ` Dave Jones

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=01072201370202.02679@starship \
    --to=phillips@bonn-fries.net \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spam-goes-to-dev-null@gmx.net \
    /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