From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/6 v5] xfs: get rid of xfs_cluster_write()
Date: Thu, 11 Feb 2016 17:45:40 +1100 [thread overview]
Message-ID: <1455173146-19535-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
Version 5 of the patchset, hopefully addressing all the remaining
review comments. I dropped the two RFC patches from this posting -
they are not necessary at this point.
Cheers,
Dave.
Version 5:
- return errors currectly when transaction allocation fails (patch
2, patch 3, patch 6)
- Added XFS_IO_INVALID to the iotype enum, and initialised the
writepage context with it. (patch 3)
- s/fail/status/ in xfs_submit_ioend (patch 6)
- pass submit_list into xfs_add_to_ioend() rather than returning the
ioend to add to the submit list (patch 6)
- fixed bug where dirty pages that are not added to an ioend would
remain dirty rather than being marked clean and transitioning
through the writeback state before returning (patch 6)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-02-11 6:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 6:45 Dave Chinner [this message]
2016-02-11 6:45 ` [PATCH 1/6] xfs: remove nonblocking mode from xfs_vm_writepage Dave Chinner
2016-02-11 6:45 ` [PATCH 2/6] xfs: remove xfs_cancel_ioend Dave Chinner
2016-02-12 9:30 ` Christoph Hellwig
2016-02-11 6:45 ` [PATCH 3/6] xfs: Introduce writeback context for writepages Dave Chinner
2016-02-11 6:45 ` [PATCH 4/6] xfs: xfs_cluster_write is redundant Dave Chinner
2016-02-11 6:45 ` [PATCH 5/6] xfs: factor mapping out of xfs_do_writepage Dave Chinner
2016-02-11 6:45 ` [PATCH 6/6] xfs: don't chain ioends during writepage submission Dave Chinner
2016-02-12 9:36 ` 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=1455173146-19535-1-git-send-email-david@fromorbit.com \
--to=david@fromorbit.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