From: Artem Bityutskiy <dedekind@infradead.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: [PATCH v2.1 00/17] abstract out the super block clean/dirty state
Date: Fri, 5 Jun 2009 16:05:38 +0300 [thread overview]
Message-ID: <1244207155-2092-1-git-send-email-dedekind@infradead.org> (raw)
Hi,
here is an updated sent of trivial patches which abstract out the super block
clean/dirty state. This is the same as v2, but it has 'sb_is_dirty()' renamed
to 'is_sb_dirty()'. The v2 patches were here:
http://marc.info/?l=linux-kernel&m=124410571830989&w=2
This patchset introduces the following 3 new helper VFS functions:
* static inline void mark_sb_dirty(struct super_block *sb)
* static inline void mark_sb_clean(struct super_block *sb)
* static inline int is_sb_dirty(struct super_block *sb)
With these patches the whole Linux kernel tree has only 3 places where
'sb->s_dirt' is referred.
These patches were previously sent as part of periodic write-back optimization
series here: http://marc.info/?l=linux-kernel&m=124342331127886&w=2
Because of the overlap with Jens' "per-bdi write-back" work, I have to work
on top of Jens' patches. However, it would be easier for me if my preparation
"abstracting sb->s_dirt" patches were merged earlier, at 2.6.31 merge window.
I think they make sense in general. I would then continue working on the second
part separately.
The patches were made on top of the VFS tree:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git for-next
commit f932bb0daca28ffe69ec876043cac00bc9b50147
Author: Theodore Ts'o <tytso@mit.edu>
Date: Tue May 12 07:37:56 2009 -0400
Fix nobh_truncate_page() to not pass stack garbage to get_block()
And they are also available at
git://git.infradead.org/users/dedekind/misc-2.6.git sb-helpers-v2
Thanks.
next reply other threads:[~2009-06-05 11:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 13:05 Artem Bityutskiy [this message]
2009-06-05 13:05 ` [PATCH v2.1 01/17] VFS: introduce helpers for manipulation s_dirty flag Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 02/17] AFFS: do not manipulate s_dirt directly Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 03/17] BFS: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 04/17] EXOFS: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 05/17] EXT2: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 06/17] EXT4: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 07/17] FAT: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 08/17] HFS: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 09/17] HFSPLUS: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 10/17] JFFS2: " Artem Bityutskiy
2009-06-06 7:25 ` David Woodhouse
2009-06-07 9:21 ` Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 11/17] NILFS: " Artem Bityutskiy
2009-06-05 12:04 ` Ryusuke Konishi
2009-06-05 13:05 ` [PATCH v2.1 12/17] reiserfs: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 13/17] SYSV: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 14/17] UDF: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 15/17] UFS: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 16/17] XFS: " Artem Bityutskiy
2009-06-05 13:05 ` [PATCH v2.1 17/17] VFS: use is_sb_dirty helper 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=1244207155-2092-1-git-send-email-dedekind@infradead.org \
--to=dedekind@infradead.org \
--cc=hch@infradead.org \
--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).