From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755727AbYEYR7g (ORCPT ); Sun, 25 May 2008 13:59:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750817AbYEYR70 (ORCPT ); Sun, 25 May 2008 13:59:26 -0400 Received: from atflat.net ([80.229.16.180]:35778 "EHLO holly.atflat.local" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750727AbYEYR70 (ORCPT ); Sun, 25 May 2008 13:59:26 -0400 X-Greylist: delayed 664 seconds by postgrey-1.27 at vger.kernel.org; Sun, 25 May 2008 13:59:25 EDT From: Tom Spink To: linux-kernel@vger.kernel.org Subject: [RFC PATCH 0/2] On-demand Filesystem Initialisation Date: Sun, 25 May 2008 18:48:17 +0100 Message-Id: <1211737699-25615-1-git-send-email-tspink@gmail.com> X-Mailer: git-send-email 1.5.4.3 In-Reply-To: <> References: <> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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(-)