From: Christoph Hellwig <hch@infradead.org>
To: Alex Elder <aelder@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 4/4] xfs: reduce the number of pagb_lock roundtrips in xfs_alloc_clear_busy
Date: Wed, 27 Apr 2011 15:45:30 -0400 [thread overview]
Message-ID: <20110427194530.GA21479@infradead.org> (raw)
In-Reply-To: <1303923381.2056.58.camel@doink>
On Wed, Apr 27, 2011 at 11:56:21AM -0500, Alex Elder wrote:
> Perhaps you have other plans that make the model you
> have here more appropriate though. Let me know
> if you intend to re-submit, otherwise I'll just take
> this version.
The discard support will call xfs_alloc_busy_clear twice for
each list, once to clear all items that don't need discarding,
and a second pass once we're done with the discards. Keeping
the sorting separate just seems cleaner at that point.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-04-27 19:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-24 19:06 [PATCH 0/4] improved busy extent handling V5 Christoph Hellwig
2011-04-24 19:06 ` [PATCH 1/4] xfs: optimize AGFL refills Christoph Hellwig
2011-04-29 0:41 ` Dave Chinner
2011-04-24 19:06 ` [PATCH 2/4] xfs: do not immediately reuse busy extent ranges Christoph Hellwig
2011-04-29 0:58 ` Dave Chinner
2011-04-24 19:06 ` [PATCH 3/4] xfs: exact busy extent tracking Christoph Hellwig
2011-04-29 1:10 ` Dave Chinner
2011-04-24 19:06 ` [PATCH 4/4] xfs: reduce the number of pagb_lock roundtrips in xfs_alloc_clear_busy Christoph Hellwig
2011-04-27 16:56 ` Alex Elder
2011-04-27 19:45 ` Christoph Hellwig [this message]
2011-04-29 1:13 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2011-04-18 6:59 [PATCH 0/4] improved busy extent handling V4 Christoph Hellwig
2011-04-18 6:59 ` [PATCH 4/4] xfs: reduce the number of pagb_lock roundtrips in xfs_alloc_clear_busy 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=20110427194530.GA21479@infradead.org \
--to=hch@infradead.org \
--cc=aelder@sgi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.