linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
	Curt Wohlgemuth <curtw@google.com>,
	linux-fsdevel@vger.kernel.org, Al Viro <viro@ZenIV.linux.org.uk>
Subject: Re: [PATCH 4/6] vfs: Reorder operations during sys_sync
Date: Thu, 20 Oct 2011 05:53:44 -0400	[thread overview]
Message-ID: <20111020095344.GD11291@infradead.org> (raw)
In-Reply-To: <1318020055-4450-5-git-send-email-jack@suse.cz>

Looks good except for some minor comments below:


Reviewed-by: Christoph Hellwig <hch@lst.de>

> diff --git a/fs/sync.c b/fs/sync.c
> index 3367d04..5fbeee6 100644
> --- a/fs/sync.c
> +++ b/fs/sync.c
> @@ -68,18 +68,26 @@ int sync_filesystem(struct super_block *sb)
>  }
>  EXPORT_SYMBOL_GPL(sync_filesystem);
>  
> -static void sync_one_sb(struct super_block *sb, void *arg)
> +static void sync_inodes_one_sb(struct super_block *sb, void *arg)
>  {
> -	if (!(sb->s_flags & MS_RDONLY))
> -		__sync_filesystem(sb, *(int *)arg);
> +	if (!(sb->s_flags & MS_RDONLY)) {
> +		if (!*(int *)arg)
> +			writeback_inodes_sb(sb);
> +		else
> +			sync_inodes_sb(sb);
> +	}

This would be a lot cleaner if you split it into two functions for
the writeback_inodes_sb and sync_inodes_sb cases.

>  }
> -/*
> - * Sync all the data for all the filesystems (called by sys_sync() and
> - * emergency sync)
> - */
> -static void sync_filesystems(int wait)
> +
> +static void sync_fs_one_sb(struct super_block *sb, void *arg)
>  {
> -	iterate_supers(sync_one_sb, &wait);
> +	if (!(sb->s_flags & MS_RDONLY) && sb->s_op->sync_fs)
> +		sb->s_op->sync_fs(sb, *(int *)arg);
> +}
> +
> +static void sync_blkdev_one_sb(struct super_block *sb, void *arg)
> +{
> +	if (!(sb->s_flags & MS_RDONLY))
> +		__sync_blockdev(sb->s_bdev, *(int *)arg);
>  }

Same here, not having these odd wait/nowait arguments whos address
is taken in the caller would make the thing a lot more readable.

It would also allow to kill of that nasty __sync_blockdev interface
eventually.


  reply	other threads:[~2011-10-20  9:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 20:40 [PATCH 0/6] Cleanup and improve sync (v3) Jan Kara
2011-10-07 20:40 ` [PATCH 1/6] vfs: Move noop_backing_dev_info check from sync into writeback Jan Kara
2011-10-20  9:48   ` Christoph Hellwig
2011-10-07 20:40 ` [PATCH 2/6] quota: Split dquot_quota_sync() to writeback and cache flushing part Jan Kara
2011-10-20  9:50   ` Christoph Hellwig
2011-10-07 20:40 ` [PATCH 3/6] quota: Move quota syncing to ->sync_fs method Jan Kara
2011-10-07 20:40 ` [PATCH 4/6] vfs: Reorder operations during sys_sync Jan Kara
2011-10-20  9:53   ` Christoph Hellwig [this message]
2011-10-20 23:57     ` Jan Kara
2011-10-07 20:40 ` [PATCH 5/6] vfs: Make sys_sync writeout also block device inodes Jan Kara
2011-10-20  9:54   ` Christoph Hellwig
2011-10-07 20:40 ` [PATCH 6/6] vfs: Avoid unnecessary WB_SYNC_NONE writeback during sys_sync and reorder sync passes Jan Kara
2011-10-20  9:57   ` Christoph Hellwig
2011-10-24 13:14     ` Jan Kara
2011-10-18  1:07 ` [PATCH 0/6] Cleanup and improve sync (v3) Jan Kara
2011-10-18  6:45   ` Christoph Hellwig

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=20111020095344.GD11291@infradead.org \
    --to=hch@infradead.org \
    --cc=curtw@google.com \
    --cc=jack@suse.cz \
    --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).