From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>,
Christoph Hellwig <hch@infradead.org>,
Zhu Han <schumi.han@gmail.com>,
xfs@oss.sgi.com
Subject: Re: Directory fsync
Date: Sun, 25 Sep 2011 20:51:07 -0400 [thread overview]
Message-ID: <20110926005107.GA12341@infradead.org> (raw)
In-Reply-To: <20110926002811.GA3159@dastard>
On Mon, Sep 26, 2011 at 10:28:11AM +1000, Dave Chinner wrote:
> All it means is that the directory fsync() is a no-op that only
> costs CPU time.
Currently it also causes a superflous cache flush, but I have a patch
in my QA queue to fix that and reduce the (already tiny) CPU overhead a
bit more.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-09-26 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-23 15:12 Directory fsync Zhu Han
2011-09-23 16:33 ` Christoph Hellwig
2011-09-23 23:09 ` Michael Monnerie
2011-09-24 1:20 ` Zhu Han
2011-10-01 23:20 ` Peter Grandi
2011-09-26 0:28 ` Dave Chinner
2011-09-26 0:51 ` Christoph Hellwig [this message]
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=20110926005107.GA12341@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=michael.monnerie@is.it-management.at \
--cc=schumi.han@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox