From: Andrew Morton <akpm@linux-foundation.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org, jengelh@computergmbh.de,
mjt@tls.msk.ru
Subject: Re: [PATCH 1/4] quota: Quota core changes for quotaon on remount
Date: Thu, 13 Mar 2008 14:48:02 -0700 [thread overview]
Message-ID: <20080313144802.7397a048.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080313130412.GG12523@duck.suse.cz>
On Thu, 13 Mar 2008 14:04:12 +0100
Jan Kara <jack@suse.cz> wrote:
> +static inline int DQUOT_ON_REMOUNT(struct super_block *sb)
> +{
> + int cnt;
> + int ret = 0, err;
> +
> + if (!sb->s_qcop || !sb->s_qcop->quota_on)
> + return -ENOSYS;
> + for (cnt = 0; cnt < MAXQUOTAS; cnt++) {
> + err = sb->s_qcop->quota_on(sb, cnt, 0, NULL, 1);
> + if (err < 0 && !ret)
> + ret = err;
> + }
> + return ret;
> +}
> +
That's about ten times too large to be inlined. Oh well.
Sometime could you please take a look at uninlining some of the porkier
functions in quotaops.h, and maybe convert them to lower case?
For the latter we can do
#define DQUOT_ON_REMOUNT(sb) dquot_on_remount(sb)
etc, then remove those macros when everything has been converted and we've
given any out-of-tree filesytem developers time to update, etc.
Thanks.
next prev parent reply other threads:[~2008-03-13 21:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 12:59 [PATCH 0/4] Automatic quotaon on remount Jan Kara
2008-03-13 13:04 ` [PATCH 1/4] quota: Quota core changes for " Jan Kara
2008-03-13 21:48 ` Andrew Morton [this message]
2008-03-17 13:17 ` Jan Kara
2008-03-13 13:04 ` [PATCH 2/4] ext3: Make ext3 handle " Jan Kara
2008-03-13 13:05 ` [PATCH 3/4] ext4: Make ext4 " Jan Kara
2008-03-13 13:06 ` [PATCH 4/4] reiserfs: Make reiserfs " Jan Kara
2008-03-13 16:37 ` [PATCH 0/4] Automatic " Christoph Hellwig
2008-03-13 16:47 ` Jan Kara
2008-03-14 2:32 ` Takashi Nishiie
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=20080313144802.7397a048.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=jengelh@computergmbh.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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).