From: Christoph Hellwig <hch@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 0/4] implement optimized fdatasync
Date: Mon, 15 Feb 2010 16:49:52 -0500 [thread overview]
Message-ID: <20100215214951.GA1036@infradead.org> (raw)
In-Reply-To: <877hqemcqz.fsf@basil.nowhere.org>
On Mon, Feb 15, 2010 at 10:04:52PM +0100, Andi Kleen wrote:
> Christoph Hellwig <hch@infradead.org> writes:
>
> > This series implements a real fdatasync, that is one that is not
> > simply identical to fdatasync, but one that skips logging the inode
>
>
> ... to fsync?
Yes, Chris Wedgwood also pointed this out privately already.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-02-15 21:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 9:44 [PATCH 0/4] implement optimized fdatasync Christoph Hellwig
2010-02-15 9:44 ` [PATCH 1/4] [PATCH 1/4] xfs: merge xfs_lrw.c into xfs_file.c Christoph Hellwig
2010-02-17 3:36 ` Dave Chinner
2010-02-17 8:14 ` Christoph Hellwig
2010-02-15 9:44 ` [PATCH 2/4] [PATCH 2/4] xfs: remove wrappers for read/write file operations Christoph Hellwig
2010-02-17 3:55 ` Dave Chinner
2010-02-17 8:31 ` Christoph Hellwig
[not found] ` <20100217211355.GR28392@discord.disaster>
2010-02-17 22:41 ` Dave Chinner
2010-02-25 20:33 ` Alex Elder
2010-02-15 9:44 ` [PATCH 3/4] [PATCH 3/4] xfs: remove wrapper for the fsync file operation Christoph Hellwig
2010-02-17 4:09 ` Dave Chinner
2010-02-17 8:33 ` Christoph Hellwig
2010-02-15 9:44 ` [PATCH 4/4] [PATCH 4/4] xfs: implement optimized fdatasync Christoph Hellwig
2010-02-17 4:17 ` Dave Chinner
2010-02-15 21:04 ` [PATCH 0/4] " Andi Kleen
2010-02-15 21:49 ` 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=20100215214951.GA1036@infradead.org \
--to=hch@infradead.org \
--cc=andi@firstfloor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox