From: Artem Bityutskiy <dedekind1@gmail.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
Linux FS Maling List <linux-fsdevel@vger.kernel.org>
Subject: [PATCH v1 0/3] do not use s_dirt in FAT FS
Date: Wed, 11 Apr 2012 14:45:04 +0300 [thread overview]
Message-ID: <1334144707-9729-1-git-send-email-dedekind1@gmail.com> (raw)
The FAT file-system uses the VFS '->write_super()' method for writing out
the FSINFO block, which contains useful but not critical information like
the amount of free clusters.
This patch-set makes FAT FS use its own mechanisms for writing-out the FSINFO
block and stop using the '->write_super()' VFS method. Namely, the FAT FS now
submits a delayed work for writing out the FSINFO block once it becomes dirty.
The reason of this exercises is to get rid of the 'sync_supers()' kernel thread.
This kernel thread wakes up every 5 (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.
Tested with xfstests.
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.
======
Overall status:
1. ext4: patches submitted, waiting for reply from Ted Ts'o:
https://lkml.org/lkml/2012/4/2/111
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
However, one patch is still not there:
http://www.spinics.net/lists/linux-ext4/msg31492.html
TODO: affs, exofs, hfs, hfsplus, jffs2, reiserfs, sysv, udf, ufs
======
Thanks,
Artem.
next reply other threads:[~2012-04-11 11:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 11:45 Artem Bityutskiy [this message]
2012-04-11 11:45 ` [PATCH v1 1/3] fat: introduce fat_mark_fsinfo_dirty helper Artem Bityutskiy
2012-04-11 11:45 ` [PATCH v1 2/3] fat: mark fsinfo as dirty less often Artem Bityutskiy
2012-04-11 11:45 ` [PATCH v1 3/3] fat: self-manage own fsinfo block Artem Bityutskiy
2012-04-13 0:12 ` [PATCH v1 0/3] do not use s_dirt in FAT FS Andrew Morton
2012-04-13 6:38 ` Artem Bityutskiy
2012-04-13 7:26 ` Andrew Morton
2012-04-13 8:45 ` 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=1334144707-9729-1-git-send-email-dedekind1@gmail.com \
--to=dedekind1@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hirofumi@mail.parknet.co.jp \
--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).