public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Chandra Seetharaman <sekharan@us.ibm.com>
Cc: xfs@oss.sgi.com
Subject: Re: [RFC v5 PATCH 2/4] xfs: Add pquota fields where gquota is used.
Date: Wed, 2 May 2012 15:49:03 -0500	[thread overview]
Message-ID: <20120502204903.GO16881@sgi.com> (raw)
In-Reply-To: <20120314202636.17044.11836.sendpatchset@chandra-lucid.austin.ibm.com>

On Wed, Mar 14, 2012 at 03:26:36PM -0500, Chandra Seetharaman wrote:
> >From 0ed09750a12c6265861415bdb431c14f8eb02437 Mon Sep 17 00:00:00 2001
> From: Chandra Seetharaman <sekharan@us.ibm.com>
> Date: Wed, 14 Mar 2012 14:17:47 -0500
> Subject: [PATCH 2/4] Add project quota changes to all the places where group quota field
>  is used.
> 
> No externally visible changed and no superblock changes, yet.

Looks like this patch does a few things:
* add separate project quota members into various structures
* split project quota and group quotas so that instead of overriding
  the group quota members incore, the new project quota members are
  used instead
* get rid of usage of the OQUOTA flag incore, in favor of separate group
  and project quota flags.
* add a project dquot argument to various functions.

> Signed-off-by: Chandra Seetharaman <sekharan@us.ibm.com>

...

> @@ -1593,9 +1662,23 @@ xfs_qm_init_quotainos(
>  			return XFS_ERROR(error);
>  		}
>  	}
> +	if (XFS_IS_PQUOTA_ON(mp) && pip == NULL) {
> +		error = xfs_qm_qino_alloc(mp, &pip,
> +					     sbflags | XFS_SB_GQUOTINO,
							^^^^
So... you're still using the group quota inode at this point.

> +					     flags | XFS_QMOPT_PQUOTA);
> +		if (error) {
> +			if (uip)
> +				IRELE(uip);
> +			if (gip)
> +				IRELE(gip);
> +
> +			return XFS_ERROR(error);
> +		}
> +	}

...

> @@ -342,9 +354,12 @@ xfs_trans_apply_dquot_deltas(
>  
>  	ASSERT(tp->t_dqinfo);
>  	qa = tp->t_dqinfo->dqa_usrdquots;
> -	for (j = 0; j < 2; j++) {
> +	for (j = 0; j < 3; j++) { /* 0 - usr, 1 - grp, 2 - prj */
>  		if (qa[0].qt_dquot == NULL) {
                    ^^^^^^^^^^^^^^^^^^^^^^
That really looks weird to me.  Can you explain what is going on there?


> -			qa = tp->t_dqinfo->dqa_grpdquots;
> +			if (qa == tp->t_dqinfo->dqa_usrdquots)
> +				qa = tp->t_dqinfo->dqa_grpdquots;
> +			else
> +				qa = tp->t_dqinfo->dqa_prjdquots;
>  			continue;

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

  reply	other threads:[~2012-05-02 20:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 20:26 [RFC v5 PATCH 0/4] xfs: Allow pquota and gquota to be used together Chandra Seetharaman
2012-03-14 20:26 ` [RFC v5 PATCH 1/4] xfs: Remove incore use of XFS_OQUOTA_ENFD and XFS_OQUOTA_CHKD Chandra Seetharaman
2012-03-14 20:26 ` [RFC v5 PATCH 2/4] xfs: Add pquota fields where gquota is used Chandra Seetharaman
2012-05-02 20:49   ` Ben Myers [this message]
2012-05-02 22:51     ` Chandra Seetharaman
2012-06-19  7:25     ` Christoph Hellwig
2012-05-04 20:00   ` Ben Myers
2012-05-04 20:04   ` Ben Myers
2012-03-14 20:26 ` [RFC v5 PATCH 3/4] xfs: Add pquotaino to on-disk super block Chandra Seetharaman
2012-05-03 17:16   ` Ben Myers
2012-05-03 20:16     ` Chandra Seetharaman
2012-05-04 19:52   ` Ben Myers
2012-03-14 20:26 ` [RFC v5 PATCH 4/4] xfs: Add a new field to fs_quota_stat to get pquota information Chandra Seetharaman

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=20120502204903.GO16881@sgi.com \
    --to=bpm@sgi.com \
    --cc=sekharan@us.ibm.com \
    --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