Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757439Ab2EGQ4A (ORCPT ); Mon, 7 May 2012 12:56:00 -0400 Received: from mga09.intel.com ([134.134.136.24]:19926 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757007Ab2EGQz6 (ORCPT ); Mon, 7 May 2012 12:55:58 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,352,1309762800"; d="scan'208";a="137865880" From: Artem Bityutskiy To: David Woodhouse , MTD Maling List Cc: Linux Kernel Maling List Subject: [PATCH v2 0/4] do not use s_dirt in JFFS2 Date: Mon, 7 May 2012 19:56:49 +0300 Message-Id: <1336409813-6365-1-git-send-email-dedekind1@gmail.com> X-Mailer: git-send-email 1.7.7.6 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2792 Lines: 62 This is the second version for the patch-set which makes JFFS2 file-system stop using the VFS '->write_supers()' call-back because I plan to remove it once all users are gone. Comparing to the previous version I gave up on using a special inode for JFFS2 because it introduces unnecessary overhead: currently JFFS2 does not register '->write_super()' at all, and if we register it for the sake of a single fake inode - it will be called for all inodes, which is unnecessary. So in this version I am using a delayed work for scheduling write-buffer flushing. v1: https://lkml.org/lkml/2012/4/11/147 The final goal is to get rid of the 'sync_supers()' kernel thread. This kernel thread wakes up every 5 seconds (by default) and calls '->write_super()' for all mounted file-systems. And the bad thing is that this is done even if all the superblocks are clean. Moreover, some file-systems do not even need this end they do not register the '->write_super()' method at all (e.g., btrfs). So 'sync_supers()' most often just generates useless wake-ups and wastes power. I am trying to make all file-systems independent of '->write_super()' and plan to remove 'sync_supers()' and '->write_super' completely once there are no more users. The '->write_supers()' method is mostly used by baroque file-systems like hfs, udf, etc. Modern file-systems like btrfs and xfs do not use it. This justifies removing this stuff from VFS completely and make every FS self-manage own superblock. Note: in the past I was trying to upstream patches which optimized 'sync_super()', but Al Viro wanted me to kill it completely instead, which I am trying to do now, see http://lkml.org/lkml/2010/7/22/96 fs/jffs2/jffs2_fs_sb.h | 4 +++ fs/jffs2/os-linux.h | 7 +---- fs/jffs2/super.c | 21 ------------------ fs/jffs2/wbuf.c | 55 +++++++++++++++++++++++++++++++++++++++++++++-- 4 files changed, 58 insertions(+), 29 deletions(-) Tested using fsstress on both nandsim and mtdram. ====== Overall status: 1. ext4: patches submitted, waiting for reply from Ted Ts'o: https://lkml.org/lkml/2012/4/2/111 Ted keeps silence so far WRT the fate of this patch-set. 2. ext2: patches are in the ext2 tree maintained by Jan Kara: git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_next 3. Version 3 of FAT FS changes were sent to Andrew and Hirofumi: https://lkml.org/lkml/2012/5/4/183 4. JFFS2 patches version 3 are sent being sent now. TODO: affs, exofs, hfs, hfsplus, reiserfs, sysv, udf, ufs ====== Thanks, Artem. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/