From mboxrd@z Thu Jan  1 00:00:00 1970
From: Artem Bityutskiy <dedekind@infradead.org>
Subject: [PATCH v2 00/17] abstract out the super block clean/dirty state
Date: Thu,  4 Jun 2009 13:41:37 +0300
Message-ID: <1244112114-23144-1-git-send-email-dedekind@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from smtp.nokia.com ([192.100.122.230]:56727 "EHLO
	mgw-mx03.nokia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1757379AbZFDIs4 (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Thu, 4 Jun 2009 04:48:56 -0400
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>

Hi,

here is a set of trivial patches which encapsulate the 'sb->s_dirt' variable
into 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 sb_is_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 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.

Thanks.