public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-xfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 1/5] xfs: don't log the entire end of the AGF
Date: Thu, 25 Aug 2016 01:09:44 -0700	[thread overview]
Message-ID: <20160825080944.GF28747@infradead.org> (raw)
In-Reply-To: <147200523494.14738.13569285576029583652.stgit@birch.djwong.org>

On Tue, Aug 23, 2016 at 07:20:35PM -0700, Darrick J. Wong wrote:
> When we're logging the last non-spare field in the AGF, we don't
> need to log the spare fields, so plumb in a new AGF logging flag
> to help us avoid that.
> 
> (This patch is already in xfsprogs.)

Looks fine, and reminds me that I need to send out my patches that
fix the SGF/AGI logging API..

Reviewed-by: Christoph Hellwig <hch@lst.de>

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

  reply	other threads:[~2016-08-25  8:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24  2:20 [PATCH 0/5] xfs: reverse mapping fixes Darrick J. Wong
2016-08-24  2:20 ` [PATCH 1/5] xfs: don't log the entire end of the AGF Darrick J. Wong
2016-08-25  8:09   ` Christoph Hellwig [this message]
2016-08-24  2:20 ` [PATCH 2/5] xfs: don't perform lookups on zero-height btrees Darrick J. Wong
2016-08-25  8:10   ` Christoph Hellwig
2016-08-24  2:20 ` [PATCH 3/5] xfs: fix some key handling problems in _btree_simple_query_range Darrick J. Wong
2016-08-25  8:10   ` Christoph Hellwig
2016-08-24  2:20 ` [PATCH 4/5] xfs: simple btree query range should look right if LE lookup fails Darrick J. Wong
2016-08-25  8:11   ` Christoph Hellwig
2016-08-24  2:20 ` [PATCH 5/5] xfs: disallow mounting of realtime + rmap filesystems Darrick J. Wong
2016-08-25  8:11   ` 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=20160825080944.GF28747@infradead.org \
    --to=hch@infradead.org \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.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