From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: hch@infradead.org, darrick.wong@oracle.com
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Damien.LeMoal@wdc.com, agruenba@redhat.com
Subject: [PATCH v4 0/2] xfs: use new list helpers in writeback code
Date: Mon, 29 Jul 2019 18:18:21 -0700 [thread overview]
Message-ID: <156444950159.2682436.1669088240015553674.stgit@magnolia> (raw)
Hi all,
>From Christoph:
This series cleans up the xfs writepage code and then lifts it to
fs/iomap/ so that it could be use by other file systems. I've been
wanting to [do] this for a while so that I could eventually convert gfs2
over to it, but I never got to it. Now Damien has a new zonefs file
system for semi-raw access to zoned block devices that would like to use
the iomap code instead of reinventing it, so I finally had to do the
work.
>From Darrick:
For v4, split the series into smaller pieces. This second part
refactors some of XFS's writeback code to use the new helpers introduced
in the first part.
Changes since v2:
- rebased to v5.3-rc1
- folded in a few changes from the gfs2 enablement series
Changes since v1:
- rebased to the latest xfs for-next tree
- keep the preallocated transactions for size updates
- rename list_pop to list_pop_entry and related cleanups
- better document the nofs context handling
- document that the iomap tracepoints are not a stable API
This series breaks up fs/iomap.c by grouping the functions by major
functional area (swapfiles, fiemap, seek hole/data, directio, buffered
io, and page migration) in separate source code files under fs/iomap/.
No functional changes have been made. Please check the copyrights to
make sure the attribution is correct.
This has been lightly tested with fstests. Enjoy!
Comments and questions are, as always, welcome.
--D
next reply other threads:[~2019-07-30 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 1:18 Darrick J. Wong [this message]
2019-07-30 1:18 ` [PATCH 1/2] xfs: initialize iomap->flags in xfs_bmbt_to_iomap Darrick J. Wong
2019-07-30 1:18 ` [PATCH 2/2] xfs: refactor the ioend merging code Darrick J. Wong
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=156444950159.2682436.1669088240015553674.stgit@magnolia \
--to=darrick.wong@oracle.com \
--cc=Damien.LeMoal@wdc.com \
--cc=agruenba@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).