From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/4 v2] xfs: get rid of xfs_cluster_write()
Date: Tue, 25 Aug 2015 15:05:49 +1000 [thread overview]
Message-ID: <1440479153-1584-1-git-send-email-david@fromorbit.com> (raw)
Hi folks,
This is the second version of the patchset that removes
xfs_cluster_write() in preference to using state in
generic_writepages to enable clustering of pages. The full
description from the v1 patchset is here:
http://oss.sgi.com/archives/xfs/2015-08/msg00224.html
The end result is effectively unchanged from version 1, just the
breakdown of the patches is different to the original posting, as
requested by Christoph.
-Dave.
Version 2:
- promote removal of non-blocking behaviour to be an initial cleanup
patch
- collapse staged introduction of struct xfs_writepage_context into
a single patch.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2015-08-25 5:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 5:05 Dave Chinner [this message]
2015-08-25 5:05 ` [PATCH 1/4] xfs: remove nonblocking mode from xfs_vm_writepage Dave Chinner
2015-08-31 18:41 ` Christoph Hellwig
2015-08-25 5:05 ` [PATCH 2/4] xfs: Introduce writeback context for writepages Dave Chinner
2015-08-31 18:02 ` Brian Foster
2015-08-31 18:56 ` Christoph Hellwig
2015-08-31 22:17 ` Dave Chinner
2015-09-01 7:41 ` Christoph Hellwig
2015-11-10 23:25 ` Dave Chinner
2015-11-11 11:32 ` Christoph Hellwig
2016-02-08 7:36 ` Christoph Hellwig
2016-02-08 7:54 ` Christoph Hellwig
2016-02-08 20:21 ` Dave Chinner
2016-02-09 9:11 ` Christoph Hellwig
2015-08-25 5:05 ` [PATCH 3/4] xfs: xfs_cluster_write is redundant Dave Chinner
2015-08-25 5:05 ` [PATCH 4/4] xfs: factor mapping out of xfs_do_writepage 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=1440479153-1584-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