public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <matthias.kaehlcke@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Ram <vshrirama@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: kernel processes - are they really needed?
Date: Wed, 31 Oct 2007 18:10:51 +0100	[thread overview]
Message-ID: <20071031171051.GG6092@traven> (raw)
In-Reply-To: <20071031160142.GC28809@atrey.karlin.mff.cuni.cz>

El Wed, Oct 31, 2007 at 05:01:42PM +0100 Jan Kara ha dit:
 
> >     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.?
>   I'll write what I know :)

i'll also put my 0.5 cents :)

> > PID  Uid     VmSize Stat Command
> >     1 root        584 S   init
> >     2 root            SWN [ksoftirqd/0]

executes (on CPU 0) the deferred parts of interrupt routines (bottom
halves), i.e. softirqs and tasklets. bad candidate for removal imo

> >     3 root            SW  [watchdog/0]
> >     4 root            SW< [events/0]

this one is in charge of executing deferred functions placed in the
default work queue. also a bad candidate for removal

> >     5 root            SW< [khelper]
> >     6 root            SW< [kthread]
> >    23 root            SW< [kblockd/0]
>   This one has something to do with block layer - like unplugging
> request queue after a certain timeout etc.
> 
> >    38 root            SW  [pdflush]
> >    39 root            SW  [pdflush]
>   Doing writeback of dirty data.
> 
> >    40 root            SW< [kswapd0]
>   Swapping pages in and out.
> 
> >    41 root            SW< [aio/0]
>   Kernel thread handling asynchronous IO.
> 
> >    85 root            SW  [mtdblockd]
> >   116 root            SWN [jffs2_gcd_mtd9]
>   jffs2 specific - ask a maintainer :) (and mtdblockd has something to
> do with MTD devices so he may know that one as well).

-- 
Matthias Kaehlcke
Linux Application Developer
Barcelona

                If you don't know where you are going,
               you will probably end up somewhere else
                         (Laurence J. Peter)
                                                                 .''`.
    using free software / Debian GNU/Linux | http://debian.org  : :'  :
                                                                `. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4                  `-

      reply	other threads:[~2007-10-31 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 13:37 kernel processes - are they really needed? Ram
2007-10-24 15:30 ` linux-os (Dick Johnson)
2007-10-24 19:43 ` Andi Kleen
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 [this message]

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=20071031171051.GG6092@traven \
    --to=matthias.kaehlcke@gmail.com \
    --cc=jack@suse.cz \
    --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