From: Al Viro <viro@ZenIV.linux.org.uk>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCHv6 0/9] kill unnecessary SB sync wake-ups + cleanups
Date: Thu, 22 Jul 2010 09:50:07 +0100 [thread overview]
Message-ID: <20100722085007.GC903@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1279785280.3044.30.camel@localhost>
On Thu, Jul 22, 2010 at 10:54:40AM +0300, Artem Bityutskiy wrote:
> On Mon, 2010-07-05 at 15:14 +0300, Artem Bityutskiy wrote:
> > here is v6 of my SB sync wakups killing patches, v5 may be found:
> > http://marc.info/?l=linux-fsdevel&m=127583599911620&w=2
> >
> > This is more of a reminder re-send, I did not get any feed-back for
> > v5. Not much changes since v5:
> >
> > 1. Drop patches which fix race conditions for s_dirty changes WRT actual
> > write-back - these things are independent and I am planning to go through
> > that separately.
> > 2. Add "Acked-by" to the btrfs patch.
> > 3. Fold all per-fs patches which introduce SB accessors into one big patch.
>
> Hi Al,
>
> you "unofficially" told me that you want to get rid of '->write_super()'
> and 'sync_supers()' should not exist. And FSes which really need
> '->write_super()' should implement that themselves.
>
> I will try to work on this, but a bit later, after my holidays. But
> could you please:
>
> 1. confirm that you want to kill '->write_super()' and '->s_dirt'
> "officially", so that I could refer to this when sending patches
ACK.
> 2. pick up patches 1-6 from this series, this would make my life easier
> a bit.
>
> I'm not sure then what do do with:
Will be in for-next tonight.
> commit 140236b4b1c749c9b795ea3d11558a0eb5a3a080
> Author: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> Date: Thu Jun 10 13:56:33 2010 +0300
>
> VFS: introduce s_dirty accessors
>
> which Linus merged, but which is now not needed, since you now want me
> to kill '->write_super()' completely. Will you take care of this please?
Once that stuff is done, we'll be able to get rid of those just fine..
FWIW, I'm tempted to add affs_dirty_sb()/affs_clean_sb()/affs_is_clean() and
corresponding helpers for other filesystems in the series and fold conversions
to those into your 1--6; you'll need insertion points for your "schedule
some work" logics whether it's done on per-fs-type basis or globally...
next prev parent reply other threads:[~2010-07-22 8:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 12:14 [PATCHv6 0/9] kill unnecessary SB sync wake-ups + cleanups Artem Bityutskiy
2010-07-05 12:14 ` [PATCHv6 1/9] AFFS: clean up dirty flag usage Artem Bityutskiy
2010-07-05 12:15 ` [PATCHv6 2/9] AFFS: wait for sb synchronization when needed Artem Bityutskiy
2010-07-05 12:15 ` [PATCHv6 3/9] BFS: clean up the superblock usage Artem Bityutskiy
2010-07-05 12:15 ` [PATCHv6 4/9] btrfs: remove junk sb_dirt change Artem Bityutskiy
2010-07-05 12:15 ` [PATCHv6 5/9] sysv: do not mark superblock dirty on mount Artem Bityutskiy
2010-07-05 12:15 ` [PATCHv6 6/9] sysv: do not mark superblock dirty on remount Artem Bityutskiy
2010-07-05 12:15 ` [PATCHv6 7/9] FS: convert all file-systems and VFS to new SB accessors Artem Bityutskiy
2010-07-05 12:15 ` [PATCHv6 8/9] VFS: rename s_dirt to s_dirty Artem Bityutskiy
2010-07-05 12:15 ` [PATCHv6 9/9] writeback: lessen sync_supers wakeup count Artem Bityutskiy
2010-07-22 7:54 ` [PATCHv6 0/9] kill unnecessary SB sync wake-ups + cleanups Artem Bityutskiy
2010-07-22 7:54 ` Artem Bityutskiy
2010-07-22 8:50 ` Al Viro [this message]
2010-07-25 9:32 ` Artem Bityutskiy
2010-07-25 9:32 ` 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=20100722085007.GC903@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dedekind1@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.