From: "Jörn Engel" <joern@logfs.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: akpm@osdl.org, linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Faster ext2_clear_inode()
Date: Mon, 9 Jul 2007 10:34:32 +0200 [thread overview]
Message-ID: <20070709083431.GA14761@lazybastard.org> (raw)
In-Reply-To: <20070709041122.GA5889@martell.zuzino.mipt.ru>
On Mon, 9 July 2007 08:11:22 +0400, Alexey Dobriyan wrote:
>
> If CONFIG_EXT2_FS_POSIX_ACL is not configured, ext2_clear_inode() will be empty
> function. However, there still will be call and immediate return which can be
> avoided.
> [...]
> +#ifdef CONFIG_EXT2_FS_POSIX_ACL
> static void ext2_clear_inode(struct inode *inode)
> {
> -#ifdef CONFIG_EXT2_FS_POSIX_ACL
> struct ext2_inode_info *ei = EXT2_I(inode);
>
> if (ei->i_acl && ei->i_acl != EXT2_ACL_NOT_CACHED) {
> @@ -197,8 +197,10 @@ static void ext2_clear_inode(struct inode *inode)
> posix_acl_release(ei->i_default_acl);
> ei->i_default_acl = EXT2_ACL_NOT_CACHED;
> }
> -#endif
> }
> +#else
> +#define ext2_clear_inode NULL
> +#endif
Are you sure your patch makes a difference? Does the resulting binary
change at all?
Jörn
--
Fancy algorithms are slow when n is small, and n is usually small.
Fancy algorithms have big constants. Until you know that n is
frequently going to be big, don't get fancy.
-- Rob Pike
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-07-09 8:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 4:11 [PATCH] Faster ext2_clear_inode() Alexey Dobriyan
2007-07-09 8:34 ` Jörn Engel [this message]
2007-07-09 18:01 ` Alexey Dobriyan
2007-07-09 20:00 ` Jörn Engel
2007-07-09 22:02 ` Dave Kleikamp
2007-07-09 22:12 ` Jörn Engel
2007-07-20 0:31 ` Andrew Morton
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=20070709083431.GA14761@lazybastard.org \
--to=joern@logfs.org \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).