From: Tom Spink <tspink@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [RFC PATCH 0/2] On-demand Filesystem Initialisation
Date: Sun, 1 Jun 2008 15:51:53 +0100 [thread overview]
Message-ID: <1212331915-22856-1-git-send-email-tspink@gmail.com> (raw)
In-Reply-To: <>
(resend to include CCs)
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!
-- Tom
fs/filesystems.c | 2 +
fs/super.c | 47 +++++++++++++++++++++++++++++++++++-
fs/xfs/linux-2.6/xfs_super.c | 55 +++++++++++++++++++++++-------------------
include/linux/fs.h | 3 ++
4 files changed, 81 insertions(+), 26 deletions(-)
next reply other threads:[~2008-06-01 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 14:51 Tom Spink [this message]
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 ` [RFC PATCH 0/2] On-demand Filesystem Initialisation Dave Chinner
2008-06-02 13:39 ` 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=1212331915-22856-1-git-send-email-tspink@gmail.com \
--to=tspink@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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).