All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/5] xfs: remove ->write_super and stop maintaining ->s_dirt
Date: Sun, 10 May 2009 11:30:04 -0500	[thread overview]
Message-ID: <4A07010C.2080305@sandeen.net> (raw)
In-Reply-To: <4A06FFF3.2090103@sandeen.net>

Eric Sandeen wrote:
> Christoph Hellwig wrote:
> 
>> the write_super method is used for
>>
>>  (1) writing back the superblock periodically from pdflush
>>  (2) called just before ->sync_fs for data integerity syncs
>>  (3) just before ->put_super
>>
>> We don't need (1) because we have our own peridoc writeout through xfssyncd,
>> we don't need (2) because xfs_fs_sync_fs performs a proper synchronous
>> superblock writeout after all other data and metadata has been written out,
>> and we don't need (3) because we synchronously write the superblock in
>> ->put_super once the filesystem is fully shut down.
>>
>> Also remove ->s_dirt tracking as it's only used to decide when too call
>> ->write_super.
>>
> Just to double check, what about sync_filesystems():
> 
>                 if (sb->s_root && (wait || sb->s_dirt))
>                         sb->s_op->sync_fs(sb, wait);
> 
> if we lose s_dirt does that mean we are potentially doing one less ->sync_fs 
> here when called with wait = 0, and is that ok?  (/me waves hands about
> sync; sync; sync magic) :)
> 
> -Eric

gah, never mind, I forgot that 0/5 talked about Jan's patches, and here:

http://lkml.indiana.edu/hypermail/linux/kernel/0904.2/03642.html

takes care of this concern.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-05-10 16:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 14:03 [PATCH 0/5] fix sync (test 182, grub) Christoph Hellwig
2009-04-26 14:03 ` [PATCH 1/5] xfs: remove ->write_super and stop maintaining ->s_dirt Christoph Hellwig
2009-05-10 16:25   ` Eric Sandeen
2009-05-10 16:30     ` Eric Sandeen [this message]
2009-05-10 17:37   ` Eric Sandeen
2009-04-26 14:03 ` [PATCH 2/5] xfs: cleanup ->sync_fs Christoph Hellwig
2009-05-10 17:51   ` Eric Sandeen
2009-05-11 20:11     ` Christoph Hellwig
2009-04-26 14:03 ` [PATCH 3/5] xfs: make inodes dirty before issuing I/O Christoph Hellwig
2009-05-10 18:02   ` Eric Sandeen
2009-04-26 14:03 ` [PATCH 4/5] xfs: make sure xfs_sync_fsdata covers the log Christoph Hellwig
2009-05-10 18:29   ` Eric Sandeen
2009-04-26 14:03 ` [PATCH 5/5] xfs: fix xfs_quiesce_data Christoph Hellwig
2009-05-10 18:37   ` Eric Sandeen
2009-05-11 20:15     ` Christoph Hellwig
2009-06-04  9:45       ` Dave Chinner
2009-06-05 10:41         ` Christoph Hellwig
2009-05-06  9:33 ` [PATCH 0/5] fix sync (test 182, grub) 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=4A07010C.2080305@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.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 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.