From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/8 v4] xfs: get rid of xfs_cluster_write
Date: Wed, 10 Feb 2016 19:47:15 +1100 [thread overview]
Message-ID: <1455094043-9694-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
This is the 4th version of this series to followup on review
comments from Brian and Christoph. There are three new patches in
this series. Patch 2/8 is split out from patch 3/8 to document the
removal of the ioend cancelling code, spearate from the introduction
of the writepage context. Patches 7 and 8 are new patches (as in the
first time I've posted them) to demonstrate how to remove the IO
completion dependency on recording the bufferehads attached to the
ioend. This is the first step in removing bufferheads from the
writepage IO path - these are FYI patches, not patches I want to
have committed immediately.
The changes all run through xfstests on 4k and 1k block size
filesystems fine, and I think i addressed all the review comments.
Patch 6/8 changed enough that I removed Brian's reviewed-by from it
and so it will need to be looked at completely again.
-Dave.
Version 4:
- split xfs_ioend_cancel removal into it's own patch (patch 2)
- cleaned up submission of ioends to be consistent w.r.t. success
and error paths (patch 3)
- made variables names less verbose (patch 6)
- got rid of xfs_writepage_submit() (patch 6)
- use a struct list_head for ioend chaining (patch 6)
- consolidated ioend submission paths to use common code (patch 6)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2016-02-10 8:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 8:47 Dave Chinner [this message]
2016-02-10 8:47 ` [PATCH 1/8] xfs: remove nonblocking mode from xfs_vm_writepage Dave Chinner
2016-02-10 8:47 ` [PATCH 2/8] xfs: remove xfs_cancel_ioend Dave Chinner
2016-02-10 11:28 ` Christoph Hellwig
2016-02-11 0:21 ` Dave Chinner
2016-02-11 15:14 ` Christoph Hellwig
2016-02-11 20:59 ` Dave Chinner
2016-02-10 8:47 ` [PATCH 3/8] xfs: Introduce writeback context for writepages Dave Chinner
2016-02-10 11:31 ` Christoph Hellwig
2016-02-11 0:25 ` Dave Chinner
2016-02-10 8:47 ` [PATCH 4/8] xfs: xfs_cluster_write is redundant Dave Chinner
2016-02-10 8:47 ` [PATCH 5/8] xfs: factor mapping out of xfs_do_writepage Dave Chinner
2016-02-10 8:47 ` [PATCH 6/8] xfs: don't chain ioends during writepage submission Dave Chinner
2016-02-10 11:36 ` Christoph Hellwig
2016-02-11 0:26 ` Dave Chinner
2016-02-11 6:39 ` Dave Chinner
2016-02-10 8:47 ` [PATCH 7/8] [RFC] xfs: build bios directly in xfs_add_to_ioend Dave Chinner
2016-02-10 8:47 ` [PATCH 8/8] [RFC] xfs: don't release bios on completion immediately Dave Chinner
2016-02-10 9:05 ` [PATCH 0/8 v4] xfs: get rid of xfs_cluster_write Christoph Hellwig
2016-02-10 18:25 ` Christoph Hellwig
2016-02-10 21:25 ` Dave Chinner
2016-02-11 15:13 ` Christoph Hellwig
2016-02-11 20:12 ` Dave Chinner
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=1455094043-9694-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 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.