From: Brian Foster <bfoster@redhat.com>
To: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2 0/7] xfs: inode transaction reservation fixups
Date: Mon, 8 Jan 2018 09:08:44 -0500 [thread overview]
Message-ID: <20180108140843.GA41128@bfoster.bfoster> (raw)
In-Reply-To: <20171130185836.18481-1-bfoster@redhat.com>
On Thu, Nov 30, 2017 at 01:58:29PM -0500, Brian Foster wrote:
> Hi all,
>
> Here's v2 of the inode tx reservation fixups. This drops the agfl fixup
> patch for the time being and adds some additional reservation fixups and
> refactoring based on Dave's feedback. This survives xfstests in a few
> different configurations and also happens to survive my inode unlink
> reservation overrun tests.
>
> Thoughts, reviews, flames appreciated.
>
> Brian
>
> v2:
> - Update AGI unlinked list and truncate reservations
> - Update commit log for ifree refactor patch.
> - Additional refactoring patches.
> - Dropped agfl fixup patch.
> v1: https://marc.info/?l=linux-xfs&m=151181428031884&w=2
>
Ping...
It looks like this is all reviewed, but perhaps just not merged yet (or
I'm just not looking in the right place)..?
Brian
> Brian Foster (7):
> xfs: print transaction log reservation on overrun
> xfs: include inobt buffers in ifree tx log reservation
> xfs: fix up agi unlinked list reservations
> xfs: truncate transaction does not modify the inobt
> xfs: include an allocfree res for inobt modifications
> xfs: refactor inode chunk alloc/free tx reservation
> xfs: eliminate duplicate icreate tx reservation functions
>
> fs/xfs/libxfs/xfs_trans_resv.c | 202 ++++++++++++++++++++---------------------
> fs/xfs/xfs_log.c | 4 +-
> 2 files changed, 99 insertions(+), 107 deletions(-)
>
> --
> 2.13.6
>
> --
> 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
next prev parent reply other threads:[~2018-01-08 14:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 18:58 [PATCH v2 0/7] xfs: inode transaction reservation fixups Brian Foster
2017-11-30 18:58 ` [PATCH v2 1/7] xfs: print transaction log reservation on overrun Brian Foster
2017-12-07 21:34 ` Darrick J. Wong
2017-11-30 18:58 ` [PATCH v2 2/7] xfs: include inobt buffers in ifree tx log reservation Brian Foster
2017-12-03 21:44 ` Dave Chinner
2017-12-07 21:40 ` Darrick J. Wong
2017-11-30 18:58 ` [PATCH v2 3/7] xfs: fix up agi unlinked list reservations Brian Foster
2017-12-03 21:45 ` Dave Chinner
2017-12-07 21:41 ` Darrick J. Wong
2017-11-30 18:58 ` [PATCH v2 4/7] xfs: truncate transaction does not modify the inobt Brian Foster
2017-12-03 21:46 ` Dave Chinner
2017-12-07 21:44 ` Darrick J. Wong
2017-11-30 18:58 ` [PATCH v2 5/7] xfs: include an allocfree res for inobt modifications Brian Foster
2017-12-07 21:47 ` Darrick J. Wong
2017-11-30 18:58 ` [PATCH v2 6/7] xfs: refactor inode chunk alloc/free tx reservation Brian Foster
2017-12-03 21:52 ` Dave Chinner
2017-12-04 12:17 ` Brian Foster
2017-12-04 12:21 ` [PATCH v3 " Brian Foster
2017-12-07 21:53 ` Darrick J. Wong
2017-11-30 18:58 ` [PATCH v2 7/7] xfs: eliminate duplicate icreate tx reservation functions Brian Foster
2017-12-03 21:54 ` Dave Chinner
2017-12-07 21:57 ` Darrick J. Wong
2018-01-08 14:08 ` Brian Foster [this message]
2018-01-08 18:06 ` [PATCH v2 0/7] xfs: inode transaction reservation fixups 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=20180108140843.GA41128@bfoster.bfoster \
--to=bfoster@redhat.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;
as well as URLs for NNTP newsgroup(s).