From: Jan Kara <jack@suse.cz>
To: Chengguang Xu <cgxu519@zoho.com.cn>
Cc: jack@suse.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext2: optimize ext2_xattr_get()
Date: Thu, 23 May 2019 16:46:12 +0200 [thread overview]
Message-ID: <20190523144612.GA18841@quack2.suse.cz> (raw)
In-Reply-To: <20190521082140.19992-1-cgxu519@zoho.com.cn>
On Tue 21-05-19 16:21:39, Chengguang Xu wrote:
> Since xattr entry names are sorted, we don't have
> to continue when current entry name is greater than
> target.
>
> Signed-off-by: Chengguang Xu <cgxu519@zoho.com.cn>
Thanks for the patch! If we are going to do these comparisons in multiple
places, then please create a helper function to do the comparison (so that
we have the same comparison in every place). Something like:
int ext2_xattr_cmp(int name_index, size_t name_len, const char *name,
struct ext2_xattr_entry *entry)
Thanks!
Honza
> ---
> fs/ext2/xattr.c | 16 ++++++++++++----
> 1 file changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/fs/ext2/xattr.c b/fs/ext2/xattr.c
> index d21dbf297b74..f1f857b83b45 100644
> --- a/fs/ext2/xattr.c
> +++ b/fs/ext2/xattr.c
> @@ -178,7 +178,7 @@ ext2_xattr_get(struct inode *inode, int name_index, const char *name,
> struct ext2_xattr_entry *entry;
> size_t name_len, size;
> char *end;
> - int error;
> + int error, not_found;
> struct mb_cache *ea_block_cache = EA_BLOCK_CACHE(inode);
>
> ea_idebug(inode, "name=%d.%s, buffer=%p, buffer_size=%ld",
> @@ -220,10 +220,18 @@ ext2_xattr_get(struct inode *inode, int name_index, const char *name,
> goto bad_block;
> if (!ext2_xattr_entry_valid(entry, inode->i_sb->s_blocksize))
> goto bad_block;
> - if (name_index == entry->e_name_index &&
> - name_len == entry->e_name_len &&
> - memcmp(name, entry->e_name, name_len) == 0)
> +
> + not_found = name_index - entry->e_name_index;
> + if (!not_found)
> + not_found = name_len - entry->e_name_len;
> + if (!not_found)
> + not_found = memcmp(name, entry->e_name,
> + name_len);
> + if (!not_found)
> goto found;
> + if (not_found < 0)
> + break;
> +
> entry = next;
> }
> if (ext2_xattr_cache_insert(ea_block_cache, bh))
> --
> 2.20.1
>
>
>
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2019-05-23 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 8:21 [PATCH] ext2: optimize ext2_xattr_get() Chengguang Xu
2019-05-23 14:46 ` Jan Kara [this message]
2019-05-24 2:07 ` cgxu519
2019-05-24 8:07 ` Jan Kara
2019-05-24 8:58 ` cgxu519
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=20190523144612.GA18841@quack2.suse.cz \
--to=jack@suse.cz \
--cc=cgxu519@zoho.com.cn \
--cc=jack@suse.com \
--cc=linux-ext4@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).