From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Jingbo Xu <jefflexu@linux.alibaba.com>,
chao@kernel.org, huyue2@coolpad.com,
linux-erofs@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, alexl@redhat.com
Subject: Re: [PATCH v2 1/2] erofs: update on-disk format for xattr name filter
Date: Wed, 5 Jul 2023 15:24:51 +0800 [thread overview]
Message-ID: <2eda59f2-a302-04a5-08de-c4ab7cf2e744@linux.alibaba.com> (raw)
In-Reply-To: <20230705070427.92579-2-jefflexu@linux.alibaba.com>
On 2023/7/5 15:04, Jingbo Xu wrote:
> The xattr name bloom filter feature is going to be introduced to speed
> up the negative xattr lookup, e.g. system.posix_acl_[access|default]
> lookup when running "ls -lR" workload.
>
> The number of common used extended attributes (n) is approximately 30.
There are some commonly used extended attributes (n) and the total number
of these is 31:
>
> trusted.overlay.opaque
> trusted.overlay.redirect
> trusted.overlay.origin
> trusted.overlay.impure
> trusted.overlay.nlink
> trusted.overlay.upper
> trusted.overlay.metacopy
> trusted.overlay.protattr
> user.overlay.opaque
> user.overlay.redirect
> user.overlay.origin
> user.overlay.impure
> user.overlay.nlink
> user.overlay.upper
> user.overlay.metacopy
> user.overlay.protattr
> security.evm
> security.ima
> security.selinux
> security.SMACK64
> security.SMACK64IPIN
> security.SMACK64IPOUT
> security.SMACK64EXEC
> security.SMACK64TRANSMUTE
> security.SMACK64MMAP
> security.apparmor
> security.capability
> system.posix_acl_access
> system.posix_acl_default
> user.mime_type
>
> Given the number of bits of the bloom filter (m) is 32, the optimal
> value for the number of the hash functions (k) is 1 (ln2 * m/n = 0.74).
>
> The single hash function is implemented as:
>
> xxh32(name, strlen(name), EROFS_XATTR_FILTER_SEED + index)
>
> where index represents the index of corresponding predefined short name
where `index`...
> prefix, while name represents the name string after stripping the above
> predefined name prefix.
>
> The constant magic number EROFS_XATTR_FILTER_SEED, i.e. 0x25BBE08F, is
> used to give a better spread when mapping these 30 extended attributes
> into 32-bit bloom filter as:
>
> bit 0: security.ima
> bit 1:
> bit 2: trusted.overlay.nlink
> bit 3:
> bit 4: user.overlay.nlink
> bit 5: trusted.overlay.upper
> bit 6: user.overlay.origin
> bit 7: trusted.overlay.protattr
> bit 8: security.apparmor
> bit 9: user.overlay.protattr
> bit 10: user.overlay.opaque
> bit 11: security.selinux
> bit 12: security.SMACK64TRANSMUTE
> bit 13: security.SMACK64
> bit 14: security.SMACK64MMAP
> bit 15: user.overlay.impure
> bit 16: security.SMACK64IPIN
> bit 17: trusted.overlay.redirect
> bit 18: trusted.overlay.origin
> bit 19: security.SMACK64IPOUT
> bit 20: trusted.overlay.opaque
> bit 21: system.posix_acl_default
> bit 22:
> bit 23: user.mime_type
> bit 24: trusted.overlay.impure
> bit 25: security.SMACK64EXEC
> bit 26: user.overlay.redirect
> bit 27: user.overlay.upper
> bit 28: security.evm
> bit 29: security.capability
> bit 30: system.posix_acl_access
> bit 31: trusted.overlay.metacopy, user.overlay.metacopy
>
> The h_name_filter field is introduced to the on-disk per-inode xattr
> header to place the corresponding xattr name filter, where bit value 1
> indicates non-existence for compatibility.
>
> This feature is indicated by EROFS_FEATURE_COMPAT_XATTR_FILTER
> compatible feature bit.
>
> Suggested-by: Alexander Larsson <alexl@redhat.com>
> Signed-off-by: Jingbo Xu <jefflexu@linux.alibaba.com>
> ---
> fs/erofs/erofs_fs.h | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/fs/erofs/erofs_fs.h b/fs/erofs/erofs_fs.h
> index 2c7b16e340fe..b4b6235fd720 100644
> --- a/fs/erofs/erofs_fs.h
> +++ b/fs/erofs/erofs_fs.h
> @@ -13,6 +13,7 @@
>
> #define EROFS_FEATURE_COMPAT_SB_CHKSUM 0x00000001
> #define EROFS_FEATURE_COMPAT_MTIME 0x00000002
> +#define EROFS_FEATURE_COMPAT_XATTR_FILTER 0x00000004
I'd suggest that if we could leave one reserved byte in the
superblock for now (and checking if it's 0) since
1) xattr filter feature is a compatible feature;
2) I'm not sure if the implementation could be changed.
so that later implementation changes won't bother compat bits
again.
>
> /*
> * Any bits that aren't in EROFS_ALL_FEATURE_INCOMPAT should
> @@ -200,7 +201,7 @@ struct erofs_inode_extended {
> * for read-only fs, no need to introduce h_refcount
> */
> struct erofs_xattr_ibody_header {
> - __le32 h_reserved;
> + __le32 h_name_filter; /* bit value 1 indicates not-present */
> __u8 h_shared_count;
> __u8 h_reserved2[7];
> __le32 h_shared_xattrs[]; /* shared xattr id array */
> @@ -221,6 +222,11 @@ struct erofs_xattr_ibody_header {
> #define EROFS_XATTR_LONG_PREFIX 0x80
> #define EROFS_XATTR_LONG_PREFIX_MASK 0x7f
>
> +#define EROFS_XATTR_FILTER_BITS 32
> +#define EROFS_XATTR_FILTER_MASK (EROFS_XATTR_FILTER_BITS - 1)
Is this useful, we could just replace it to
(EROFS_XATTR_FILTER_BITS - 1) directly.
Otherwise it looks good to me,
Thanks,
Gao Xiang
next prev parent reply other threads:[~2023-07-05 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 7:04 [PATCH v2 0/2] erofs: introduce xattr name bloom filter Jingbo Xu
2023-07-05 7:04 ` [PATCH v2 1/2] erofs: update on-disk format for xattr name filter Jingbo Xu
2023-07-05 7:24 ` Gao Xiang [this message]
2023-07-05 7:43 ` Alexander Larsson
2023-07-05 7:51 ` Gao Xiang
2023-07-05 8:12 ` Alexander Larsson
2023-07-05 8:13 ` Gao Xiang
2023-07-05 7:04 ` [PATCH v2 2/2] erofs: boost negative xattr lookup with bloom filter Jingbo Xu
2023-07-05 7:44 ` Alexander Larsson
2023-07-05 7:55 ` Gao Xiang
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=2eda59f2-a302-04a5-08de-c4ab7cf2e744@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=alexl@redhat.com \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@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