public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
	Chris Cottam <chris.cottam@bytemark.co.uk>,
	linux-xfs@vger.kernel.org
Subject: Re: XFS reflinks
Date: Wed, 30 Aug 2017 08:03:16 +1000	[thread overview]
Message-ID: <20170829220316.GD10621@dastard> (raw)
In-Reply-To: <20170829162310.GA22552@infradead.org>

On Tue, Aug 29, 2017 at 09:23:10AM -0700, Christoph Hellwig wrote:
> On Tue, Aug 29, 2017 at 09:03:08AM -0700, Darrick J. Wong wrote:
> > First, should we land the incore extent map rework (not that I've seen a
> > patchset yet) so that the increased extent map fragmentation resulting
> > from cow/dedupe don't overwhelm the memory allocator with high order
> > allocations?  Incore extent map memory usage hasn't been an issue here...
> 
> Working on this now, but so far this hasn't been a major issue.
> The main workload where the extent list currently hurts and that
> prompted my work in this area doesn't even involve reflinks (sparse
> VM image).

Yup, that's a problem, and it's going to be even more of a problem
once people start using reflink to snapshot sparse VM images. I
think that the extent rework is probably the most important thing we
need to solve for COW to be generally usable.

Christoph, ignoring the CoW consideration, this is top of my list of
"things we've been ignoring for too long that need to be fixed
ASAP". I've got the time to work on this right now, so if you don't
have time to get it done in the next merge cycle I can probably make
that happen....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2017-08-29 22:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 11:23 XFS reflinks Chris Cottam
2017-08-29 13:00 ` Christoph Hellwig
2017-08-29 13:39   ` Chris Cottam
2017-08-29 16:40     ` Christoph Hellwig
2017-08-29 16:03   ` Darrick J. Wong
2017-08-29 16:23     ` Christoph Hellwig
2017-08-29 22:03       ` Dave Chinner [this message]
2017-08-30  7:03         ` Christoph Hellwig
2017-08-31 10:33         ` Chris Cottam
2017-08-31 13:09           ` Christoph Hellwig

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=20170829220316.GD10621@dastard \
    --to=david@fromorbit.com \
    --cc=chris.cottam@bytemark.co.uk \
    --cc=darrick.wong@oracle.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