linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: [PATCH 0/6] xfs: basic cow fork speculative preallocation
Date: Mon, 28 Nov 2016 14:09:35 -0500	[thread overview]
Message-ID: <1480360181-20396-1-git-send-email-bfoster@redhat.com> (raw)

Hi all,

Here is a first legitimate pass at COW fork speculative preallocation.
Updates from the previously posted rfc are noted below. Highlights are
inclusion of the COW fork fiemap patch, support for throttling
preallocation on low free space conditions and refactoring tweaks to
create a separate helper for the data fork -> COW fork lookup sequence.
Other changes are minor updates based on review of the rfc. Note that I
decided to retain patch 3 as an independent patch and hopefully explain
it a bit better. We can still squash it into the subsequent patch if
warranted, however.

The xfs_io patch to take advantage of COW fork fiemap is available here:

  http://www.spinics.net/lists/linux-xfs/msg01710.html

This survives xfstests with the exception of generic/305, which appears
to just be a case of hardcoded accounting in the golden output file
changing due to preallocation. I'll have to figure out the best way to
deal with that (a preceding eofb scan perhaps?). Thoughts, reviews,
flames appreciated.

Brian

v1:
- Rebase onto for-next (new iext lookup helpers).
- Split off speculative prealloc refactor patches into separate series.
- Prepend the COW fork fiemap patch.
- Create xfs_iomap_search_extents() helper for data/COW fork extent
  lookup.
- Reuse xfs_iomap_prealloc_size() to incorporate prealloc throttling.
- Added patch to reclaim cowblocks on write failure due to ENOSPC.
rfc: http://www.spinics.net/lists/linux-xfs/msg02152.html

Brian Foster (6):
  xfs: fiemap support for cow fork
  xfs: refactor iomap delalloc existing extent search into helper
  xfs: logically separate iomap range from allocation range
  xfs: reuse iomap delalloc code for COW fork reservation
  xfs: free cowblocks and retry on buffered write ENOSPC
  xfs: implement basic COW fork speculative preallocation

 fs/xfs/xfs_file.c           |   1 +
 fs/xfs/xfs_iomap.c          | 315 +++++++++++++++++++++++++++++++++-----------
 fs/xfs/xfs_iomap.h          |   1 +
 fs/xfs/xfs_iops.c           |   4 +
 include/uapi/linux/fiemap.h |   1 +
 5 files changed, 244 insertions(+), 78 deletions(-)

-- 
2.7.4


             reply	other threads:[~2016-11-28 19:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-28 19:09 Brian Foster [this message]
2016-11-28 19:09 ` [PATCH 1/6] xfs: fiemap support for cow fork Brian Foster
2016-11-28 19:15   ` Darrick J. Wong
2016-11-28 19:31     ` Brian Foster
2016-11-30 19:30       ` Christoph Hellwig
2016-11-28 19:09 ` [PATCH 2/6] xfs: refactor iomap delalloc existing extent search into helper Brian Foster
2016-11-30  1:15   ` Darrick J. Wong
2016-11-28 19:09 ` [PATCH 3/6] xfs: logically separate iomap range from allocation range Brian Foster
2016-11-30  1:21   ` Darrick J. Wong
2016-11-28 19:09 ` [PATCH 4/6] xfs: reuse iomap delalloc code for COW fork reservation Brian Foster
2016-11-28 19:09 ` [PATCH 5/6] xfs: free cowblocks and retry on buffered write ENOSPC Brian Foster
2016-11-28 19:09 ` [PATCH 6/6] xfs: implement basic COW fork speculative preallocation Brian Foster

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=1480360181-20396-1-git-send-email-bfoster@redhat.com \
    --to=bfoster@redhat.com \
    --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).