linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Jan Kara <jack@suse.cz>, Curt Wohlgemuth <curtw@google.com>,
	linux-fsdevel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes
Date: Tue, 3 Jul 2012 16:47:57 +0200	[thread overview]
Message-ID: <20120703144757.GE27388@quack.suse.cz> (raw)
In-Reply-To: <20120622103041.GF14083@ZenIV.linux.org.uk>

On Fri 22-06-12 11:30:41, Al Viro wrote:
> On Wed, Jun 20, 2012 at 10:03:36PM +0200, Jan Kara wrote:
> >   Hi Curt,
> > 
> > On Wed 20-06-12 07:23:56, Curt Wohlgemuth wrote:
> > > Was there ever a resolution for this patch and the series?  I looked
> > > for but found no ack/nack for V4 of your "Cleanup and improve sync"
> > > patch series.
> > > 
> > > We've been carrying a crappy hack/patch to sync all block device
> > > inodes in order to allow lilo to not break, and it'd be nice to have a
> > > real fix for it upstream.
> >   The patch set works, just I'm missing some final review and someone (Al?)
> > has to pick it up and merge it. Anyway I plan to repost the series soon to
> > hopefully get things moving again...
> 
> Please, rebase and send them my way.
  OK, I've rebased the patches, updated the measurements (numbers have
changed somewhat since last time), and sent them your way.

									Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2012-07-03 14:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 23:46 [PATCH 0/8 RESEND] Cleanup and improve sync (v4) Jan Kara
2012-01-05 23:46 ` [PATCH 1/8] vfs: Move noop_backing_dev_info check from sync into writeback Jan Kara
2012-01-05 23:46 ` [PATCH 2/8] quota: Split dquot_quota_sync() to writeback and cache flushing part Jan Kara
2012-01-05 23:46 ` [PATCH 3/8] quota: Move quota syncing to ->sync_fs method Jan Kara
2012-01-05 23:46 ` [PATCH 4/8] vfs: Reorder operations during sys_sync Jan Kara
2012-01-05 23:46 ` [PATCH 5/8] vfs: Create function for iterating over block devices Jan Kara
2012-01-05 23:46 ` [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes Jan Kara
2012-06-20 14:23   ` Curt Wohlgemuth
2012-06-20 20:03     ` Jan Kara
2012-06-22 10:30       ` Al Viro
2012-07-03 14:47         ` Jan Kara [this message]
2012-01-05 23:46 ` [PATCH 7/8] vfs: Remove unnecessary flushing of block devices Jan Kara
2012-01-05 23:46 ` [PATCH 8/8] vfs: Avoid unnecessary WB_SYNC_NONE writeback during sys_sync and reorder sync passes Jan Kara
  -- strict thread matches above, loose matches on Subject: below --
2012-07-03 14:45 [PATCH 0/8 v4] Flush all block devices on sync(2) and cleanup the code Jan Kara
2012-07-03 14:45 ` [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes Jan Kara
2012-07-17  6:27   ` Fengguang Wu
2012-07-20  2:21     ` Fengguang Wu
2011-11-09 17:44 [PATCH 0/8] Cleanup and improve sync (v4) Jan Kara
2011-11-09 17:45 ` [PATCH 6/8] vfs: Make sys_sync writeout also block device inodes Jan Kara

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=20120703144757.GE27388@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=curtw@google.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@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).