| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: [Jfs-discussion] Unneeded kernel threads (xfs, jfs, gfs2) |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 13 May 2008 05:21:56 -0400 |
| Cc: | Georgi Chorbadzhiyski <gf@xxxxxxxxxxx>, cluster-devel@xxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, jfs-discussion@xxxxxxxxxxxxxxxxxxxxx, Donald Douwsma <donaldd@xxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <20080513090311.GZ155679365@sgi.com> |
| References: | <4828CAC6.3090402@unixsol.org> <48292742.8090409@sgi.com> <482951C3.60600@unixsol.org> <20080513090311.GZ155679365@sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
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. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Unneeded kernel threads (xfs, jfs, gfs2), David Chinner |
|---|---|
| Next by Date: | Re: [Jfs-discussion] Unneeded kernel threads (xfs, jfs, gfs2), Christoph Hellwig |
| Previous by Thread: | Re: Unneeded kernel threads (xfs, jfs, gfs2), David Chinner |
| Next by Thread: | Re: [Jfs-discussion] Unneeded kernel threads (xfs, jfs, gfs2), Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |