From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Brian Foster <bfoster@redhat.com>,
xfs <linux-xfs@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC PATCH] xfs: try to avoid blowing out the transaction reservation when bunmaping a shared extent
Date: Thu, 27 Apr 2017 00:35:19 -0700 [thread overview]
Message-ID: <20170427073519.GA18392@infradead.org> (raw)
In-Reply-To: <20170426213731.GC23371@birch.djwong.org>
On Wed, Apr 26, 2017 at 02:37:31PM -0700, Darrick J. Wong wrote:
> That's so shockingly obvious I don't know why it didn't occur to me.
> Uh, I'll go give that a try with that horrid generic/931 testcase that
> I sent to the list a couple of weeks ago. :)
I like the idea too. But once thing to remember is that freeing
blocks from two AG in the same transaction is deadlock prone as the
other thread shows. I've been doing some work to mitigate that, but
I guess I'll just wait for your new patch and will rebase on top of
that.
next prev parent reply other threads:[~2017-04-27 7:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 2:09 [RFC PATCH] xfs: try to avoid blowing out the transaction reservation when bunmaping a shared extent Darrick J. Wong
2017-04-26 13:59 ` Brian Foster
2017-04-26 21:37 ` Darrick J. Wong
2017-04-27 7:35 ` Christoph Hellwig [this message]
2017-04-28 19:40 ` Darrick J. Wong
2017-05-01 14:58 ` Brian Foster
2017-05-02 8:00 ` Christoph Hellwig
2017-05-02 12:05 ` Brian Foster
2017-05-04 11:59 ` Christoph Hellwig
2017-05-04 13:40 ` Brian Foster
2017-04-27 7:40 ` Christoph Hellwig
2017-04-27 15:58 ` Darrick J. Wong
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=20170427073519.GA18392@infradead.org \
--to=hch@infradead.org \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.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