From: Christoph Hellwig <hch@lst.de>
To: dhowells@redhat.com
Cc: linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org
Subject: afs_fsync
Date: Sun, 18 Apr 2010 21:46:53 +0200 [thread overview]
Message-ID: <20100418194653.GA20069@lst.de> (raw)
Dave,
I've been looking at afs_fsync a bit lately and don't quite
understanding what's going on there. As of 2.6.32 we always
write out all data before calling into ->fsync. From my very
unscientific exploration into afs_fsync it's doing exactly that
data writeout again, just in a rather complicated way, and
then marks the inode as having dirty pages again, which is not
very helpful inside ->fsync. Any chance you could explain
what's really going on there?
next reply other threads:[~2010-04-18 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 19:46 Christoph Hellwig [this message]
2010-04-19 11:54 ` afs_fsync David Howells
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=20100418194653.GA20069@lst.de \
--to=hch@lst.de \
--cc=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@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 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).