From: Ben Myers <bpm@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/8] log all inode updates V3
Date: Thu, 8 Mar 2012 14:08:55 -0600 [thread overview]
Message-ID: <20120308200855.GY7762@sgi.com> (raw)
In-Reply-To: <20120229095347.009884687@bombadil.infradead.org>
On Wed, Feb 29, 2012 at 04:53:47AM -0500, Christoph Hellwig wrote:
> Changes since V2:
> - address more review feedback
>
> Changes since V1:
> - address all review feedback
> - reimplement an optimized fdatasync
I believe this series is ready to go except for my concern about
xfs_ioend_is_append, which needs to go over all of the ioends in order
to determine whether an append is possible, not just the first.
-Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-03-08 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 9:53 [PATCH 0/8] log all inode updates V3 Christoph Hellwig
2012-02-29 9:53 ` [PATCH 1/8] xfs: use per-filesystem I/O completion workqueues Christoph Hellwig
2012-02-29 9:53 ` [PATCH 2/8] xfs: do not require an ioend for new EOF calculation Christoph Hellwig
2012-02-29 9:53 ` [PATCH 6/8] xfs: make xfs_inode_item_size idempotent Christoph Hellwig
2012-03-02 16:31 ` Mark Tinguely
2012-03-07 21:02 ` Ben Myers
2012-02-29 9:53 ` [PATCH 7/8] xfs: split in-core and on-disk inode log item fields Christoph Hellwig
2012-03-02 19:40 ` Mark Tinguely
2012-03-08 18:40 ` Ben Myers
2012-02-29 9:53 ` [PATCH 8/8] xfs: reimplement fdatasync support Christoph Hellwig
2012-03-02 21:04 ` Mark Tinguely
2012-03-08 20:06 ` Ben Myers
2012-03-08 20:08 ` Ben Myers [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=20120308200855.GY7762@sgi.com \
--to=bpm@sgi.com \
--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.