From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: xiakaixu1987@gmail.com
Cc: linux-xfs@vger.kernel.org, Kaixu Xia <kaixuxia@tencent.com>
Subject: Re: [PATCH v4 2/3] xfs: check tp->t_dqinfo value instead of the XFS_TRANS_DQ_DIRTY flag
Date: Mon, 26 Oct 2020 15:51:29 -0700 [thread overview]
Message-ID: <20201026225129.GE347246@magnolia> (raw)
In-Reply-To: <1602130749-23093-3-git-send-email-kaixuxia@tencent.com>
On Thu, Oct 08, 2020 at 12:19:08PM +0800, xiakaixu1987@gmail.com wrote:
> From: Kaixu Xia <kaixuxia@tencent.com>
>
> Nowadays the only things that the XFS_TRANS_DQ_DIRTY flag seems to do
> are indicates the tp->t_dqinfo->dqs[XFS_QM_TRANS_{USR,GRP,PRJ}] values
> changed and check in xfs_trans_apply_dquot_deltas() and the unreserve
> variant xfs_trans_unreserve_and_mod_dquots(). Actually, we also can
> use the tp->t_dqinfo value instead of the XFS_TRANS_DQ_DIRTY flag, that
> is to say, we allocate the new tp->t_dqinfo only when the qtrx values
> changed, so the tp->t_dqinfo value isn't NULL equals the XFS_TRANS_DQ_DIRTY
> flag is set, we only need to check if tp->t_dqinfo == NULL in
> xfs_trans_apply_dquot_deltas() and its unreserve variant to determine
> whether lock all of the dquots and join them to the transaction.
>
> Signed-off-by: Kaixu Xia <kaixuxia@tencent.com>
Woooooo!!
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> ---
> fs/xfs/libxfs/xfs_shared.h | 1 -
> fs/xfs/xfs_inode.c | 8 +-------
> fs/xfs/xfs_trans_dquot.c | 13 ++-----------
> 3 files changed, 3 insertions(+), 19 deletions(-)
>
> diff --git a/fs/xfs/libxfs/xfs_shared.h b/fs/xfs/libxfs/xfs_shared.h
> index c795ae47b3c9..8c61a461bf7b 100644
> --- a/fs/xfs/libxfs/xfs_shared.h
> +++ b/fs/xfs/libxfs/xfs_shared.h
> @@ -62,7 +62,6 @@ void xfs_log_get_max_trans_res(struct xfs_mount *mp,
> #define XFS_TRANS_SB_DIRTY 0x02 /* superblock is modified */
> #define XFS_TRANS_PERM_LOG_RES 0x04 /* xact took a permanent log res */
> #define XFS_TRANS_SYNC 0x08 /* make commit synchronous */
> -#define XFS_TRANS_DQ_DIRTY 0x10 /* at least one dquot in trx dirty */
> #define XFS_TRANS_RESERVE 0x20 /* OK to use reserved data blocks */
> #define XFS_TRANS_NO_WRITECOUNT 0x40 /* do not elevate SB writecount */
> #define XFS_TRANS_RES_FDBLKS 0x80 /* reserve newly freed blocks */
> diff --git a/fs/xfs/xfs_inode.c b/fs/xfs/xfs_inode.c
> index 2bfbcf28b1bd..4d2cebaa3637 100644
> --- a/fs/xfs/xfs_inode.c
> +++ b/fs/xfs/xfs_inode.c
> @@ -959,7 +959,6 @@ xfs_dir_ialloc(
> xfs_buf_t *ialloc_context = NULL;
> int code;
> void *dqinfo;
> - uint tflags;
>
> tp = *tpp;
> ASSERT(tp->t_flags & XFS_TRANS_PERM_LOG_RES);
> @@ -1018,12 +1017,9 @@ xfs_dir_ialloc(
> * and attach it to the next transaction.
> */
> dqinfo = NULL;
> - tflags = 0;
> if (tp->t_dqinfo) {
> dqinfo = (void *)tp->t_dqinfo;
> tp->t_dqinfo = NULL;
> - tflags = tp->t_flags & XFS_TRANS_DQ_DIRTY;
> - tp->t_flags &= ~(XFS_TRANS_DQ_DIRTY);
> }
>
> code = xfs_trans_roll(&tp);
> @@ -1031,10 +1027,8 @@ xfs_dir_ialloc(
> /*
> * Re-attach the quota info that we detached from prev trx.
> */
> - if (dqinfo) {
> + if (dqinfo)
> tp->t_dqinfo = dqinfo;
> - tp->t_flags |= tflags;
> - }
>
> if (code) {
> xfs_buf_relse(ialloc_context);
> diff --git a/fs/xfs/xfs_trans_dquot.c b/fs/xfs/xfs_trans_dquot.c
> index 67f1e275b34d..0ebfd7930382 100644
> --- a/fs/xfs/xfs_trans_dquot.c
> +++ b/fs/xfs/xfs_trans_dquot.c
> @@ -84,13 +84,6 @@ xfs_trans_dup_dqinfo(
>
> xfs_trans_alloc_dqinfo(ntp);
>
> - /*
> - * Because the quota blk reservation is carried forward,
> - * it is also necessary to carry forward the DQ_DIRTY flag.
> - */
> - if (otp->t_flags & XFS_TRANS_DQ_DIRTY)
> - ntp->t_flags |= XFS_TRANS_DQ_DIRTY;
> -
> for (j = 0; j < XFS_QM_TRANS_DQTYPES; j++) {
> oqa = otp->t_dqinfo->dqs[j];
> nqa = ntp->t_dqinfo->dqs[j];
> @@ -270,8 +263,6 @@ xfs_trans_mod_dquot(
>
> if (delta)
> trace_xfs_trans_mod_dquot_after(qtrx);
> -
> - tp->t_flags |= XFS_TRANS_DQ_DIRTY;
> }
>
>
> @@ -348,7 +339,7 @@ xfs_trans_apply_dquot_deltas(
> int64_t totalbdelta;
> int64_t totalrtbdelta;
>
> - if (!(tp->t_flags & XFS_TRANS_DQ_DIRTY))
> + if (!tp->t_dqinfo)
> return;
>
> ASSERT(tp->t_dqinfo);
> @@ -490,7 +481,7 @@ xfs_trans_unreserve_and_mod_dquots(
> struct xfs_dqtrx *qtrx, *qa;
> bool locked;
>
> - if (!tp->t_dqinfo || !(tp->t_flags & XFS_TRANS_DQ_DIRTY))
> + if (!tp->t_dqinfo)
> return;
>
> for (j = 0; j < XFS_QM_TRANS_DQTYPES; j++) {
> --
> 2.20.0
>
next prev parent reply other threads:[~2020-10-26 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 4:19 [PATCH v4 0/3] xfs: random fixes for disk quota xiakaixu1987
2020-10-08 4:19 ` [PATCH v4 1/3] xfs: delete duplicated tp->t_dqinfo null check and allocation xiakaixu1987
2020-10-09 11:32 ` Brian Foster
2020-10-26 22:51 ` Darrick J. Wong
2020-10-08 4:19 ` [PATCH v4 2/3] xfs: check tp->t_dqinfo value instead of the XFS_TRANS_DQ_DIRTY flag xiakaixu1987
2020-10-09 11:32 ` Brian Foster
2020-10-26 22:51 ` Darrick J. Wong [this message]
2020-10-08 4:19 ` [PATCH v4 3/3] xfs: directly return if the delta equal to zero xiakaixu1987
2020-10-09 11:32 ` Brian Foster
2020-10-10 1:50 ` kaixuxia
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=20201026225129.GE347246@magnolia \
--to=darrick.wong@oracle.com \
--cc=kaixuxia@tencent.com \
--cc=linux-xfs@vger.kernel.org \
--cc=xiakaixu1987@gmail.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;
as well as URLs for NNTP newsgroup(s).