From: Dave Chinner <david@fromorbit.com>
To: Tom Spink <tspink@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: [RFC PATCH 0/2] On-demand Filesystem Initialisation
Date: Mon, 2 Jun 2008 11:58:39 +1000 [thread overview]
Message-ID: <20080602015831.GB2428@disturbed> (raw)
In-Reply-To: <1212331915-22856-1-git-send-email-tspink@gmail.com>
On Sun, Jun 01, 2008 at 03:51:53PM +0100, Tom Spink wrote:
>
> (resend to include CCs)
What cc's? Still no xfs cc on it. I added it to this reply....
> This (short) patch series is another RFC for the patch that introduces on-demand
> filesystem initialisation. In addition to the original infrastructure
> implementation (with clean-ups), it changes XFS to use this new infrastructure.
>
> I wrote a toy filesystem (testfs) to simulate scheduling/allocation delays and
> to torture the mount/unmount cycles. I didn't manage to deadlock the system
> in my tests. XFS also works as expected aswell, in that the global threads
> are not created until an XFS filesystem is mounted for the first time. When the
> last XFS filesystem is unmounted, the threads go away.
>
> Please let me know what you think!
Why even bother? This is why we have /modular/ kernels - if you're
not using XFS then don't load it and you won't see those pesky
threads. That'll save on a bunch of memory as well because the xfs
module ain't small (>480k on i386)....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-06-02 1:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 14:51 [RFC PATCH 0/2] On-demand Filesystem Initialisation Tom Spink
2008-06-01 14:51 ` [RFC PATCH 1/2] vfs: Introduce on-demand filesystem initialisation Tom Spink
2008-06-01 14:51 ` [RFC PATCH 2/2] xfs: Make XFS use the new file system init infrastructure Tom Spink
2008-06-01 15:32 ` [RFC PATCH 1/2] vfs: Introduce on-demand filesystem initialisation Al Viro
2008-06-02 13:38 ` Tom Spink
2008-06-02 1:58 ` Dave Chinner [this message]
2008-06-02 13:39 ` [RFC PATCH 0/2] On-demand Filesystem Initialisation Tom Spink
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=20080602015831.GB2428@disturbed \
--to=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tspink@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).