public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 10/10] xfs: intent item whiteouts
Date: Wed, 4 May 2022 11:49:29 +1000	[thread overview]
Message-ID: <20220504014929.GF1098723@dread.disaster.area> (raw)
In-Reply-To: <20220503225009.GE8265@magnolia>

On Tue, May 03, 2022 at 03:50:09PM -0700, Darrick J. Wong wrote:
> On Wed, May 04, 2022 at 08:17:28AM +1000, Dave Chinner wrote:
> > @@ -985,6 +993,13 @@ xlog_cil_build_lv_chain(
> >  
> >  		item = list_first_entry(&cil->xc_cil,
> >  					struct xfs_log_item, li_cil);
> > +
> > +		if (test_bit(XFS_LI_WHITEOUT, &item->li_flags)) {
> > +			list_move(&item->li_cil, whiteouts);
> > +			trace_xfs_cil_whiteout_skip(item);
> > +			continue;
> > +		}
> > +
> >  		list_del_init(&item->li_cil);
> >  		if (!ctx->lv_chain)
> >  			ctx->lv_chain = item->li_lv;
> > @@ -1000,6 +1015,19 @@ xlog_cil_build_lv_chain(
> >  	}
> >  }
> >  
> > +static void
> > +xlog_cil_push_cleanup_whiteouts(
> 
> Pushing cleanup whiteouts?
> 
> Oh, clean up whiteouts as part of pushing CIL.
> 
> I almost want to ask for a comment here:
> 
> /* Remove log items from the CIL that have been elided from the checkpoint. */
> static void
> xlog_cil_push_cleanup_whiteouts(
> 
> But fmeh, aside from my own momentary confusion this isn't that big of a
> deal.

Oh, fair comment - it's not consistent with other helpers that
are just named xlog_cil_<thing>, like xlog_cil_build_lv_chain().

I dropped the "push" out of the name.

> Reviewed-by: Darrick J. Wong <djwong@kernel.org>

Thanks!

-Dave.
-- 
Dave Chinner
david@fromorbit.com

      reply	other threads:[~2022-05-04  2:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 22:17 [PATCH 00/10 v6] xfs: intent whiteouts Dave Chinner
2022-05-03 22:17 ` [PATCH 01/10] xfs: zero inode fork buffer at allocation Dave Chinner
2022-05-03 22:41   ` Darrick J. Wong
2022-05-03 22:42   ` Alli
2022-05-10 12:47   ` Christoph Hellwig
2022-05-03 22:17 ` [PATCH 02/10] xfs: fix potential log item leak Dave Chinner
2022-05-03 22:42   ` Alli
2022-05-03 22:44   ` Darrick J. Wong
2022-05-10 12:48   ` Christoph Hellwig
2022-05-03 22:17 ` [PATCH 03/10] xfs: hide log iovec alignment constraints Dave Chinner
2022-05-03 22:45   ` Darrick J. Wong
2022-05-03 23:07     ` Dave Chinner
2022-05-03 22:17 ` [PATCH 04/10] xfs: don't commit the first deferred transaction without intents Dave Chinner
2022-05-03 22:17 ` [PATCH 05/10] xfs: add log item flags to indicate intents Dave Chinner
2022-05-03 22:17 ` [PATCH 06/10] xfs: tag transactions that contain intent done items Dave Chinner
2022-05-03 22:17 ` [PATCH 07/10] xfs: factor and move some code in xfs_log_cil.c Dave Chinner
2022-05-03 22:17 ` [PATCH 08/10] xfs: add log item method to return related intents Dave Chinner
2022-05-03 22:17 ` [PATCH 09/10] xfs: whiteouts release intents that are not in the AIL Dave Chinner
2022-05-10 12:49   ` Christoph Hellwig
2022-05-03 22:17 ` [PATCH 10/10] xfs: intent item whiteouts Dave Chinner
2022-05-03 22:42   ` Alli
2022-05-03 22:50   ` Darrick J. Wong
2022-05-04  1:49     ` Dave Chinner [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=20220504014929.GF1098723@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --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