From: Georgi Chorbadzhiyski <gf@unixsol.org>
To: Jan Engelhardt <jengelh@medozas.de>
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 11:36:02 +0300 [thread overview]
Message-ID: <482952F2.3080608@unixsol.org> (raw)
In-Reply-To: <alpine.LNX.1.10.0805130115090.25441@fbirervta.pbzchgretzou.qr>
Jan Engelhardt mumbled something about, On 5/13/08 2:21 AM:
> On Tuesday 2008-05-13 00:55, Georgi Chorbadzhiyski wrote:
>> Not needed here, because no jfs partition is in use.
>> Not needed here, because no xfs partition is in use.
>> I dont use gfs2
>
> You miss the best of Linux. So, why not unload the modules?
ext3 is working just fine for now, thanks (:
>>> 1141 ? S< 0:00 \_ [block-osm/1]
>> What is osm? Can't find anything in kernel config?
>
> drivers/message/i2o/i2o_block.c:#define OSM_NAME "block-osm"
>
>>> 1148 ? S< 0:00 \_ [khpsbpkt]
>> What is this?
>
> ieee1394/ieee1394_core.c:static struct task_struct *khpsbpkt_thread;
Strange names :)
--
Georgi Chorbadzhiyski
http://georgi.unixsol.org/
next prev parent reply other threads:[~2008-05-13 8:35 UTC|newest]
Thread overview: 16+ 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 [this message]
2008-05-14 17:22 ` [Cluster-devel] " Stefan Richter
2008-05-14 17:22 ` Stefan Richter
2008-05-13 5:29 ` Donald Douwsma
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 ` [Cluster-devel] Re: [Jfs-discussion] " Christoph Hellwig
2008-05-13 9:21 ` Christoph Hellwig
2008-05-13 9:28 ` [Cluster-devel] " 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=482952F2.3080608@unixsol.org \
--to=gf@unixsol.org \
--cc=cluster-devel@redhat.com \
--cc=jengelh@medozas.de \
--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 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.