public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: steve@digidescorp.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] FAT: optimize FSINFO writeback
Date: Wed, 01 Jul 2009 05:57:15 +0900	[thread overview]
Message-ID: <87ocs5h238.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <1246392130-4261-1-git-send-email-steve@digidescorp.com> (steve@digidescorp.com's message of "Tue, 30 Jun 2009 15:02:10 -0500")

steve@digidescorp.com writes:

> Only write the FSINFO block back to disk when its contents change.
> This optimization can be important when the underlying physical media
> can wear out, i.e. Flash.

I have no objection to this though.  Was this tested on recent version?
Well, now, we are using sb->s_dirty for fsinfo, so I'm wondering why
this happen frequently.

Thanks.

> Signed-off-by: Steven J. Magnani <steve@digidescorp.com>
> ---
> diff -uprN a/fs/fat/misc.c b/fs/fat/misc.c
> --- a/fs/fat/misc.c	2009-06-29 11:12:40.000000000 -0500
> +++ b/fs/fat/misc.c	2009-06-29 11:46:45.000000000 -0500
> @@ -61,11 +61,25 @@ void fat_clusters_flush(struct super_blo
>  		       le32_to_cpu(fsinfo->signature2),
>  		       sbi->fsinfo_sector);
>  	} else {
> -		if (sbi->free_clusters != -1)
> -			fsinfo->free_clusters = cpu_to_le32(sbi->free_clusters);
> -		if (sbi->prev_free != -1)
> -			fsinfo->next_cluster = cpu_to_le32(sbi->prev_free);
> -		mark_buffer_dirty(bh);
> +		char write_needed = 0;
> +		__le32 le_value;
> +
> +		if (sbi->free_clusters != -1) {
> +			le_value = cpu_to_le32(sbi->free_clusters);
> +			if (fsinfo->free_clusters != le_value) {
> +				fsinfo->free_clusters = le_value;
> +				write_needed = 1;
> +			}
> +		}
> +		if (sbi->prev_free != -1) {
> +			le_value = cpu_to_le32(sbi->prev_free);
> +			if (fsinfo->next_cluster != le_value) {
> +				fsinfo->next_cluster = le_value;
> +				write_needed = 1;
> +			}
> +		}
> +		if (write_needed)
> +			mark_buffer_dirty(bh);
>  	}
>  	brelse(bh);
>  }
>

-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2009-06-30 20:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 20:02 [PATCH] FAT: optimize FSINFO writeback steve
2009-06-30 20:57 ` OGAWA Hirofumi [this message]
2009-06-30 22:19   ` Steven J. Magnani
2009-07-01  0:28     ` OGAWA Hirofumi
2009-07-01 13:07       ` Steven J. Magnani

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=87ocs5h238.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve@digidescorp.com \
    /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