All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "peter k." <spam-goes-to-dev-null@gmx.net>
Cc: "David Schwartz" <davids@webmaster.com>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.7: wtf is "ksoftirqd_CPU0"
Date: Sat, 21 Jul 2001 13:36:05 -0300	[thread overview]
Message-ID: <20010721133605.C3667@conectiva.com.br> (raw)
In-Reply-To: <NOEJJDACGOHCKNCOGFOMCECBCKAA.davids@webmaster.com> <002f01c11202$60f22100$c20e9c3e@host1>
In-Reply-To: <002f01c11202$60f22100$c20e9c3e@host1>; from spam-goes-to-dev-null@gmx.net on Sat, Jul 21, 2001 at 06:29:37PM +0200

Em Sat, Jul 21, 2001 at 06:29:37PM +0200, peter k. escreveu:
> 
> > > 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's the kernel soft IRQ daemon. It provides a context from which to
> > execute 'slow' code that was triggered by an interrupt. There will be one
> > per CPU.
> 
> why wasnt it run in previous kernels? im just wondering why it suddenly

because previous kernels had problems that Andrea's approach fixes? Read
the archives for the thread about it.

- Arnaldo

  reply	other threads:[~2001-07-21 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <NOEJJDACGOHCKNCOGFOMCECBCKAA.davids@webmaster.com>
2001-07-21 16:29 ` 2.4.7: wtf is "ksoftirqd_CPU0" peter k.
2001-07-21 16:36   ` Arnaldo Carvalho de Melo [this message]
2001-07-21 17:15   ` Dave Jones
2001-07-21 16:08 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-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=20010721133605.C3667@conectiva.com.br \
    --to=acme@conectiva.com.br \
    --cc=davids@webmaster.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.