public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] avoid busy extents during user data allocations
Date: Fri, 4 Mar 2011 08:19:44 -0500	[thread overview]
Message-ID: <20110304131944.GA31536@infradead.org> (raw)
In-Reply-To: <20110304125953.650347660@bombadil.infradead.org>

On Fri, Mar 04, 2011 at 07:59:53AM -0500, Christoph Hellwig wrote:
> This patchset adds support to trim down extents

Sorry, sent this out before finishing up the introduction.

This patchset adds support for trimming down allocations of user data
to avoid busy extents.  I'm actually not quite sure it's overly useful
in this form, as we're much better off allowing free reallocation
between data extents, and only avoid busy extents coming from freed
metadata.  Neverless I'd like to get a review of the new search
algorithm in patch 3, especially for the nice comments explaining it
all, based on a mail from Dave.

Patches 1 and 2 on the other hand are simple cleanups which I think
should go into the tree ASAP.

The other patches from the previous submitting are back to the drawing
board - implementing Dave's suggestion of skipping busy extents for
metadata to user data reallocation promises to give a lot of speedups,
but making it work with the requirement to track freed extents for
discard purposes isn't quite trivial as we might have to remove extents
from the busy list during reallocations, which requires additional
infrastructure to lock the list of busy extents in the transaction / cil
context which isn't there yet, and additional exclusion of allocations
from ongoing discards.

> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
---end quoted text---

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      parent reply	other threads:[~2011-03-04 13:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 12:59 [PATCH 0/3] avoid busy extents during user data allocations Christoph Hellwig
2011-03-04 12:59 ` [PATCH 1/3] xfs: clean up the xfs_alloc_compute_aligned calling convention Christoph Hellwig
2011-03-04 12:59 ` [PATCH 3/3] xfs: do not immediately reuse busy extent ranges Christoph Hellwig
2011-03-07 23:01   ` Alex Elder
2011-03-09 11:11     ` Christoph Hellwig
2011-03-04 13:19 ` Christoph Hellwig [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=20110304131944.GA31536@infradead.org \
    --to=hch@infradead.org \
    --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