mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Ram <vshrirama@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel processes - are they really needed?
Date: Wed, 24 Oct 2007 21:43:07 +0200	[thread overview]
Message-ID: <p73hckgqoxg.fsf@bingen.suse.de> (raw)
In-Reply-To: <8bf247760710240637w686f1a2fxdf63a649787eca25@mail.gmail.com> (Ram's message of "Wed\, 24 Oct 2007 19\:07\:02 +0530")

Ram <vshrirama@gmail.com> writes:

> Hi,
>     When i do ps -l. i see the following processes which are obviously
> started by kernel.
>
>    Could any one tell me what each of these processes do 

> and can anyone of them can be removed.?

Some of them can probably. Or rather many depending on the configuration.

Sometimes there are good reasons for an own thread, but often there are also 
bad reasons.

If the threads don't sleep or have special requirements long they
should generally just use keventd instead.

Unfortunately a lot of people seem to think they're cheap because 
it's relatively easy to create them using work queues now, so we end
up with more and more all the time.

Especially on systems with many cores or threads which end up with a
lot of dubious per CPU threads. Some scaling up is needed, but one per CPU 
seems to be generally too many.

My favourite for a ridiculous thread was and is "kpsmoused" 

-Andi

  parent reply	other threads:[~2007-10-24 19:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 13:37 Ram
2007-10-24 15:30 ` linux-os (Dick Johnson)
2007-10-24 19:43 ` Andi Kleen [this message]
2007-10-31 16:35   ` Dmitry Torokhov
2007-10-31 17:33     ` Andi Kleen
2007-11-02  1:51       ` Dmitry Torokhov
2007-10-31 16:01 ` Jan Kara
2007-10-31 17:10   ` Matthias Kaehlcke

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=p73hckgqoxg.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vshrirama@gmail.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

Powered by JetHome