From: Artem Bityutskiy <dedekind1@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/6] hfs: stop using write_supers and s_dirt
Date: Tue, 12 Jun 2012 11:13:32 +0300 [thread overview]
Message-ID: <1339488818-14461-1-git-send-email-dedekind1@gmail.com> (raw)
This patch-set makes HFS file-system stop using the VFS '->write_supers()'
call-back and the '->s_dirt' superblock field because I plan to remove them
once all users are gone.
Like the other similar patch-sets, we switch to a delayed job for writing out
the superblock instead of using the 's_dirt' flag. Additionally, this patch-set
includes several clean-ups.
Reminder:
The 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, many 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.
Al, in the past I was trying to upstream patches which optimized 'sync_super()',
but you wanted me to kill it completely instead, which I am trying to do
now, see http://lkml.org/lkml/2010/7/22/96
Tested using the fsstress test from the LTP project.
======
Overall status:
1. ext4: patches submitted, waiting for review from Ted Ts'o:
https://lkml.org/lkml/2012/4/2/111
2. udf: patch submitted, should be in Jan Kara's tree:
https://lkml.org/lkml/2012/6/4/233
3 exofs: patch submitted, not sure if it will go to the exofs tree:
https://lkml.org/lkml/2012/6/4/211
4. affs: patches submitted, should be in Al Viro's tree:
https://lkml.org/lkml/2012/6/6/400
4. ext2: done, see commit f72cf5e223a28d3b3ea7dc9e40464fd534e359e8
5. vfat: done, see commit 78491189ddb6d84d4a4abae992ed891a236d0263
6. jffs2: done, see commit 208b14e507c00ff7f108e1a388dd3d8cc805a443
7. reiserfs: done, see commit 033369d1af1264abc23bea2e174aa47cdd212f6f
TODO: hfsplus, sysv, ufs
======
fs/hfs/extent.c | 2 +-
fs/hfs/hfs_fs.h | 15 +++++++----
fs/hfs/inode.c | 14 +++-------
fs/hfs/mdb.c | 15 +++++++++++
fs/hfs/super.c | 73 +++++++++++++++++++++++++++----------------------------
5 files changed, 65 insertions(+), 54 deletions(-)
Thanks,
Artem.
next reply other threads:[~2012-06-12 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 8:13 Artem Bityutskiy [this message]
2012-06-12 8:13 ` [PATCH 1/6] hfs: push lock_super down Artem Bityutskiy
2012-06-12 8:13 ` [PATCH 2/6] hfs: get rid of lock_super Artem Bityutskiy
2012-06-12 8:13 ` [PATCH 3/6] hfs: remove extra mdb write on unmount Artem Bityutskiy
2012-06-12 8:13 ` [PATCH 4/6] hfs: simplify a bit checking for R/O Artem Bityutskiy
2012-06-12 8:13 ` [PATCH 5/6] hfs: introduce VFS superblock object back-reference Artem Bityutskiy
2012-06-12 8:13 ` [PATCH 6/6] hfs: get rid of hfs_sync_super Artem Bityutskiy
2012-07-02 14:15 ` Artem Bityutskiy
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=1339488818-14461-1-git-send-email-dedekind1@gmail.com \
--to=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).