From: Jan Kara <jack@suse.cz>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: tytso@mit.edu, uekawa@chromium.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] tune2fs: do not update quota when not needed
Date: Thu, 12 Sep 2024 11:15:58 +0200 [thread overview]
Message-ID: <20240912091558.jbmwtnvfxrymjch2@quack3> (raw)
In-Reply-To: <20240830185921.2690798-1-gwendal@chromium.org>
On Fri 30-08-24 11:59:21, Gwendal Grignou wrote:
> Enabling quota is expensive: All inodes in the filesystem are scanned.
> Only do it when the requested quota configuration does not match the
> existing configuration.
>
> Test:
> Add a tiny patch to print out when core of function
> handle_quota_options() is triggered.
> Issue commands:
> truncate -s 1G unused ; mkfs.ext4 unused
>
> | commands | trigger | comments
> +---------------------------------------------------------+---------+---------
> | tune2fs -Qusrquota,grpquota -Qprjquota -O quota unused | Y |
> Quota not set at formatting.
> | tune2fs -Qusrquota,grpquota -Qprjquota -O quota unused | N |
> Already set just above
> | tune2fs -Qusrquota,grpquota -Q^prjquota -O quota unused | Y |
> Disabling a quota option always force a deep look.
> | tune2fs -Qusrquota,grpquota -Q^prjquota -O quota unused | Y |
> See just above
> | tune2fs -Qusrquota,grpquota -O quota unused | N |
> No change from previous line.
> | tune2fs -Qusrquota,^grpquota -O quota unused | Y |
> Disabling a quota option always force a deep look.
> | tune2fs -Qusrquota -O quota unused | N |
> No change from previous line.
> | tune2fs -O ^quota unused | Y |
> Remove quota
> | tune2fs -O quota unused | X |
> function handle_quota_options() not called, default values
> (-Qusrquota,grpquota) used.
> | tune2fs -O quota -Qusrquota unused | N |
> Already set just above
Good idea. One comment regarding the code:
> diff --git a/misc/tune2fs.c b/misc/tune2fs.c
> index 6de40e93..3cce8861 100644
> --- a/misc/tune2fs.c
> +++ b/misc/tune2fs.c
> @@ -1804,6 +1804,41 @@ static int handle_quota_options(ext2_filsys fs)
> qtype_bits |= 1 << qtype;
> }
>
> + /*
> + * Check if the filesystem already has quota enabled and more features
> + * need to be enabled and are not, or some features need to be disabled.
> + */
> + if (ext2fs_has_feature_quota(fs->super) && qtype_bits) {
> + for (qtype = 0 ; qtype < MAXQUOTAS; qtype++) {
> + if ((quota_enable[qtype] == QOPT_ENABLE &&
> + *quota_sb_inump(fs->super, qtype) == 0) ||
> + (quota_enable[qtype] == QOPT_DISABLE)) {
> + /* Some work needed to match the configuration. */
> + break;
> + }
> + }
> + if (qtype == MAXQUOTAS) {
> + /* Nothing to do. */
> + return 0;
> + }
> + }
> + /*
> + * Check if the user wants all features disabled and it is already
> + * the case.
> + */
> + if (!ext2fs_has_feature_quota(fs->super) && !qtype_bits) {
> + for (qtype = 0 ; qtype < MAXQUOTAS; qtype++) {
> + if (*quota_sb_inump(fs->super, qtype)) {
> + /* Some work needed to match the configuration. */
> + break;
> + }
> + }
> + if (qtype == MAXQUOTAS) {
> + /* Nothing to do. */
> + return 0;
> + }
> + }
Why don't you do it like:
for (qtype = 0 ;qtype < MAXQUOTAS; qtype++) {
if (quota_enable[qtype] == QOPT_ENABLE &&
*quota_sb_inump(fs->super, qtype) == 0) {
/* Need to enable this quota type. */
break;
}
if (quota_enable[qtype] == QOPT_DISABLE &&
*quota_sb_inump(fs->super, qtype)) {
/* Need to disable this quota type. */
break;
}
}
if (qtype == MAXQUOTAS) {
/* Nothing to do. */
return 0;
}
As far as I can tell this should result in similar decisions and should be
much easier to understand what's going on...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-09-12 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 18:59 [PATCH] tune2fs: do not update quota when not needed Gwendal Grignou
2024-09-12 9:15 ` Jan Kara [this message]
2024-10-25 2:53 ` Theodore Ts'o
2025-01-03 23:47 ` Gwendal Grignou
2025-01-03 23:50 ` [PATCH v2] " Gwendal Grignou
2025-01-06 10:10 ` Jan Kara
2025-05-21 14:51 ` Theodore Ts'o
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=20240912091558.jbmwtnvfxrymjch2@quack3 \
--to=jack@suse.cz \
--cc=gwendal@chromium.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=uekawa@chromium.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