From: Al Viro <viro@ZenIV.linux.org.uk>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
tytso@mit.edu, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/1] VFS: introduce s_dirty accessors
Date: Fri, 11 Jun 2010 02:42:53 +0100 [thread overview]
Message-ID: <20100611014253.GE31073@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1276167393-31492-2-git-send-email-dedekind1@gmail.com>
On Thu, Jun 10, 2010 at 01:56:33PM +0300, Artem Bityutskiy wrote:
> From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
>
> This patch introduces 3 VFS accessors: 'sb_mark_dirty()',
> 'sb_mark_clean()', and 'sb_is_dirty()'. They simply
> set 'sb->s_dirt' or test 'sb->s_dirt'. The plan is to make
> every FS use these accessors later instead of manipulating
> the 'sb->s_dirt' flag directly.
>
> Ultimately, this change is a preparation for the periodic
> superblock synchronization optimization which is about
> preventing the "sync_supers" kernel thread from waking up
> even if there is nothing to synchronize.
>
> This patch does not do any functional change, just adds
> accessor functions.
Applied and pushed. It's in for-next, which should do until Linus
comes back and picks it...
next prev parent reply other threads:[~2010-06-11 1:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 10:56 [PATCH 0/1] VFS: introduce s_dirty accessors Artem Bityutskiy
2010-06-10 10:56 ` [PATCH 1/1] " Artem Bityutskiy
2010-06-11 1:42 ` Al Viro [this message]
2010-07-05 13:04 ` [PATCH 0/1] " Artem Bityutskiy
2010-07-09 22:27 ` tytso
2010-07-09 22:31 ` Andrew Morton
2010-07-10 4:33 ` 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=20100611014253.GE31073@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=dedekind1@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).