[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1244207155-2092-1-git-send-email-dedekind@infradead.org>
Date: Fri, 5 Jun 2009 16:05:38 +0300
From: Artem Bityutskiy <dedekind@...radead.org>
To: Al Viro <viro@...IV.linux.org.uk>
Cc: linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Christoph Hellwig <hch@...radead.org>
Subject: [PATCH v2.1 00/17] abstract out the super block clean/dirty state
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@....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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists