From: Christoph Hellwig <hch@infradead.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [Jfs-discussion] Unneeded kernel threads (xfs, jfs, gfs2)
Date: Tue, 13 May 2008 05:21:56 -0400 [thread overview]
Message-ID: <20080513092156.GA26736@infradead.org> (raw)
In-Reply-To: <20080513090311.GZ155679365@sgi.com>
On Tue, May 13, 2008 at 07:03:11PM +1000, David Chinner wrote:
> Sure - XFS will start another three kernel threads per filesystem
> that gets mounted. And for good measure, it cleans them up again
> on unmount. :)
>
> The other threads are per-cpu workqueue threads that are shared
> across all XFS filesystems in the system and hence are started
> when XFS is initialised rather than when a mount occurs.
Well, we could refcount the number of active xfs instances and
start/stop the global threads based on that. Not really worth my
time IHMO, but if someone comes up with a clean enough patch it should
go in.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: David Chinner <dgc@sgi.com>
Cc: Georgi Chorbadzhiyski <gf@unixsol.org>,
cluster-devel@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jfs-discussion@lists.sourceforge.net,
Donald Douwsma <donaldd@sgi.com>,
xfs@oss.sgi.com
Subject: Re: [Jfs-discussion] Unneeded kernel threads (xfs, jfs, gfs2)
Date: Tue, 13 May 2008 05:21:56 -0400 [thread overview]
Message-ID: <20080513092156.GA26736@infradead.org> (raw)
In-Reply-To: <20080513090311.GZ155679365@sgi.com>
On Tue, May 13, 2008 at 07:03:11PM +1000, David Chinner wrote:
> Sure - XFS will start another three kernel threads per filesystem
> that gets mounted. And for good measure, it cleans them up again
> on unmount. :)
>
> The other threads are per-cpu workqueue threads that are shared
> across all XFS filesystems in the system and hence are started
> when XFS is initialised rather than when a mount occurs.
Well, we could refcount the number of active xfs instances and
start/stop the global threads based on that. Not really worth my
time IHMO, but if someone comes up with a clean enough patch it should
go in.
next prev parent reply other threads:[~2008-05-13 9:21 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
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 ` Christoph Hellwig [this message]
2008-05-13 9:21 ` [Jfs-discussion] " 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=20080513092156.GA26736@infradead.org \
--to=hch@infradead.org \
/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.