From: Brian Foster <bfoster@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2 0/5] xfs: basic cow fork speculative preallocation
Date: Mon, 16 Jan 2017 11:26:58 -0500 [thread overview]
Message-ID: <20170116162658.GC6302@bfoster.bfoster> (raw)
In-Reply-To: <20170113171342.GC27605@infradead.org>
On Fri, Jan 13, 2017 at 09:13:42AM -0800, Christoph Hellwig wrote:
> On Wed, Jan 11, 2017 at 12:54:04PM -0500, Brian Foster wrote:
> > Hi all,
> >
> > Here's v2 of the cow fork speculative prealloc patches. No major changes
> > here, as outlined below. Thoughts on any of this?
>
> Any results? Better performance, less extents for certain workloads?
Sorry, I neglected to pull that forward from the rfc. That discussion is
here:
http://www.spinics.net/lists/linux-xfs/msg02152.html
I should probably repeat some of this testing at this point, but the
general result is a reduction in extent count for parallel cow fork
allocator workloads. E.g., attempting to address the same problem of
parallel data fork allocators competing for contiguous space, resolved
by traditional speculative preallocation.
I was also kind of thinking about whether this could work around the
need to have a default cowextsz hint at all, allowing that feature to be
used more like the traditional extent size hint as well. This is
distinctly more aggressive for use cases like large vm image files,
however. At the same time, the idea is to make it transparent enough
that it shouldn't really affect the user (i.e., via throttling,
background and on demand reclaim, also just like normal preallocation).
Brian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-01-16 16:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 17:54 [PATCH v2 0/5] xfs: basic cow fork speculative preallocation Brian Foster
2017-01-11 17:54 ` [PATCH v2 1/5] xfs: refactor iomap delalloc existing extent search into helper Brian Foster
2017-01-11 17:54 ` [PATCH v2 2/5] xfs: logically separate iomap range from allocation range Brian Foster
2017-01-11 17:54 ` [PATCH v2 3/5] xfs: reuse iomap delalloc code for COW fork reservation Brian Foster
2017-01-13 17:13 ` Christoph Hellwig
2017-01-16 16:26 ` Brian Foster
2017-01-16 17:37 ` Christoph Hellwig
2017-01-16 19:04 ` Brian Foster
2017-01-11 17:54 ` [PATCH v2 4/5] xfs: free cowblocks and retry on buffered write ENOSPC Brian Foster
2017-01-13 17:12 ` Christoph Hellwig
2017-01-11 17:54 ` [PATCH v2 5/5] xfs: implement basic COW fork speculative preallocation Brian Foster
2017-01-13 17:13 ` [PATCH v2 0/5] xfs: basic cow " Christoph Hellwig
2017-01-16 16:26 ` Brian Foster [this message]
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=20170116162658.GC6302@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=hch@infradead.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).