public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chandan Babu R <chandanrlinux@gmail.com>
To: Allison Henderson <allison.henderson@oracle.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v18 10/11] xfs: Add delay ready attr remove routines
Date: Thu, 29 Apr 2021 13:23:15 +0530	[thread overview]
Message-ID: <87fsz9a5n8.fsf@garuda> (raw)
In-Reply-To: <20210428080919.20331-11-allison.henderson@oracle.com>

On 28 Apr 2021 at 13:39, Allison Henderson wrote:
> This patch modifies the attr remove routines to be delay ready. This
> means they no longer roll or commit transactions, but instead return
> -EAGAIN to have the calling routine roll and refresh the transaction. In
> this series, xfs_attr_remove_args is merged with
> xfs_attr_node_removename become a new function, xfs_attr_remove_iter.
> This new version uses a sort of state machine like switch to keep track
> of where it was when EAGAIN was returned. A new version of
> xfs_attr_remove_args consists of a simple loop to refresh the
> transaction until the operation is completed. A new XFS_DAC_DEFER_FINISH
> flag is used to finish the transaction where ever the existing code used
> to.
>
> Calls to xfs_attr_rmtval_remove are replaced with the delay ready
> version __xfs_attr_rmtval_remove. We will rename
> __xfs_attr_rmtval_remove back to xfs_attr_rmtval_remove when we are
> done.
>
> xfs_attr_rmtval_remove itself is still in use by the set routines (used
> during a rename).  For reasons of preserving existing function, we
> modify xfs_attr_rmtval_remove to call xfs_defer_finish when the flag is
> set.  Similar to how xfs_attr_remove_args does here.  Once we transition
> the set routines to be delay ready, xfs_attr_rmtval_remove is no longer
> used and will be removed.
>
> This patch also adds a new struct xfs_delattr_context, which we will use
> to keep track of the current state of an attribute operation. The new
> xfs_delattr_state enum is used to track various operations that are in
> progress so that we know not to repeat them, and resume where we left
> off before EAGAIN was returned to cycle out the transaction. Other
> members take the place of local variables that need to retain their
> values across multiple function recalls.  See xfs_attr.h for a more
> detailed diagram of the states.
>

Sorry, My previous response to this patch was incorrectly formatted. Fixing it
now.

The error handling issues pointed out in the previous version of the this
patch have been fixed.

Reviewed-by: Chandan Babu R <chandanrlinux@gmail.com>

--
chandan

  parent reply	other threads:[~2021-04-29  7:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  8:09 [PATCH v18 00/11] Delay Ready Attributes Allison Henderson
2021-04-28  8:09 ` [PATCH v18 01/11] xfs: Reverse apply 72b97ea40d Allison Henderson
2021-04-28  8:09 ` [PATCH v18 02/11] xfs: Add xfs_attr_node_remove_name Allison Henderson
2021-04-28  8:09 ` [PATCH v18 03/11] xfs: Hoist xfs_attr_set_shortform Allison Henderson
2021-04-28  8:09 ` [PATCH v18 04/11] xfs: Add helper xfs_attr_set_fmt Allison Henderson
2021-04-28  8:09 ` [PATCH v18 05/11] xfs: Separate xfs_attr_node_addname and xfs_attr_node_addname_clear_incomplete Allison Henderson
2021-04-29  7:40   ` Chandan Babu R
2021-04-28  8:09 ` [PATCH v18 06/11] xfs: Add helper xfs_attr_node_addname_find_attr Allison Henderson
2021-04-28  8:09 ` [PATCH v18 07/11] xfs: Hoist xfs_attr_node_addname Allison Henderson
2021-04-28  8:09 ` [PATCH v18 08/11] xfs: Hoist xfs_attr_leaf_addname Allison Henderson
2021-04-28  8:09 ` [PATCH v18 09/11] xfs: Hoist node transaction handling Allison Henderson
2021-04-28  8:09 ` [PATCH v18 10/11] xfs: Add delay ready attr remove routines Allison Henderson
2021-04-29  7:49   ` Chandan Babu R
2021-04-29  7:53   ` Chandan Babu R [this message]
2021-04-29 14:07   ` Brian Foster
2021-04-28  8:09 ` [PATCH v18 11/11] xfs: Add delay ready attr set routines Allison Henderson

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=87fsz9a5n8.fsf@garuda \
    --to=chandanrlinux@gmail.com \
    --cc=allison.henderson@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