From: Donald Douwsma <donaldd@sgi.com>
To: Georgi Chorbadzhiyski <gf@unixsol.org>
Cc: xfs@oss.sgi.com, jfs-discussion@lists.sourceforge.net,
cluster-devel@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Unneeded kernel threads (xfs, jfs, gfs2)
Date: Tue, 13 May 2008 15:29:38 +1000 [thread overview]
Message-ID: <48292742.8090409@sgi.com> (raw)
In-Reply-To: <4828CAC6.3090402@unixsol.org>
Georgi Chorbadzhiyski wrote:
> Hi guys, I know that not all kernel thread users are converted to
> start only when needed but the following is little annoying specially
> when I'm not even using jfs, xfs and gfs2.
>
> Look at the ps output from a standard distro 2.6.24.5 kernel after a
> fresh boot:
...
>
> Kernel config can be found here:
> http://mirrors.unixsol.org/slackware/slackware-12.1/kernels/hugesmp.s/config
>
Your distro is building all of these modules into the kernel.
CONFIG_XFS_FS=y
CONFIG_JFS_FS=y
CONFIG_GFS2_FS=y
This isnt exactly standard practice, normally they'd be set to =m and only
used if required to mount a filesystem. You may want to ask the slackware
people why they chose to do this for their hugexxx.s kernels.
Don
next prev parent reply other threads:[~2008-05-13 5:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 22:55 Unneeded kernel threads (xfs, jfs, gfs2) Georgi Chorbadzhiyski
2008-05-12 23:21 ` Jan Engelhardt
2008-05-13 8:36 ` Georgi Chorbadzhiyski
2008-05-14 17:22 ` Stefan Richter
2008-05-13 5:29 ` Donald Douwsma [this message]
2008-05-13 5:51 ` FD Cami
2008-05-13 8:33 ` Georgi Chorbadzhiyski
2008-05-13 8:30 ` Georgi Chorbadzhiyski
2008-05-13 9:03 ` David Chinner
2008-05-13 9:21 ` [Jfs-discussion] " Christoph Hellwig
2008-05-13 9:28 ` Christoph Hellwig
2008-05-13 15:31 ` Eric Sandeen
2008-05-13 13:31 ` Lennart Sorensen
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=48292742.8090409@sgi.com \
--to=donaldd@sgi.com \
--cc=cluster-devel@redhat.com \
--cc=gf@unixsol.org \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.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