From: JeffleXu <jefflexu@linux.alibaba.com>
To: Jia Zhu <zhujia.zj@bytedance.com>,
linux-erofs@lists.ozlabs.org, xiang@kernel.org, chao@kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
yinxin.x@bytedance.com, huyue2@coolpad.com
Subject: Re: [PATCH V2 5/5] erofs: support fscache based shared domain
Date: Tue, 13 Sep 2022 14:27:51 +0800 [thread overview]
Message-ID: <097a8ffb-c8b0-ed10-6c82-8a6de9bed09b@linux.alibaba.com> (raw)
In-Reply-To: <20220902105305.79687-6-zhujia.zj@bytedance.com>
On 9/2/22 6:53 PM, Jia Zhu wrote:
> Several erofs filesystems can belong to one domain, and data blobs can
> be shared among these erofs filesystems of same domain.
>
> Users could specify domain_id mount option to create or join into a domain.
>
> Signed-off-by: Jia Zhu <zhujia.zj@bytedance.com>
> ---
> fs/erofs/fscache.c | 73 +++++++++++++++++++++++++++++++++++++++++++++
> fs/erofs/internal.h | 12 ++++++++
> fs/erofs/super.c | 10 +++++--
> 3 files changed, 93 insertions(+), 2 deletions(-)
>
> diff --git a/fs/erofs/fscache.c b/fs/erofs/fscache.c
> index 439dd3cc096a..c01845808ede 100644
> --- a/fs/erofs/fscache.c
> +++ b/fs/erofs/fscache.c
> @@ -559,12 +559,27 @@ int erofs_fscache_register_cookie(struct super_block *sb,
> void erofs_fscache_unregister_cookie(struct erofs_fscache **fscache)
> {
> struct erofs_fscache *ctx = *fscache;
> + struct erofs_domain *domain;
>
> if (!ctx)
> return;
> + domain = ctx->domain;
> + if (domain) {
> + mutex_lock(&domain->mutex);
> + /* Cookie is still in use */
> + if (atomic_read(&ctx->anon_inode->i_count) > 1) {
> + iput(ctx->anon_inode);
> + mutex_unlock(&domain->mutex);
> + return;
> + }
> + iput(ctx->anon_inode);
> + kfree(ctx->name);
> + mutex_unlock(&domain->mutex);
> + }
>
> fscache_unuse_cookie(ctx->cookie, NULL, NULL);
> fscache_relinquish_cookie(ctx->cookie, false);
> + erofs_fscache_domain_put(domain);
> ctx->cookie = NULL;
>
> iput(ctx->inode);
> @@ -609,3 +624,61 @@ void erofs_fscache_unregister_fs(struct super_block *sb)
> sbi->volume = NULL;
> sbi->domain = NULL;
> }
> +
> +static int erofs_fscache_domain_init_cookie(struct super_block *sb,
> + struct erofs_fscache **fscache, char *name, bool need_inode)
> +{
> + int ret;
> + struct inode *inode;
> + struct erofs_fscache *ctx;
> + struct erofs_sb_info *sbi = EROFS_SB(sb);
> + struct erofs_domain *domain = sbi->domain;
> +
> + ret = erofs_fscache_register_cookie(sb, &ctx, name, need_inode);
> + if (ret)
> + return ret;
> +
> + ctx->name = kstrdup(name, GFP_KERNEL);
> + if (!ctx->name)
> + return -ENOMEM;
Shall we clean up the above registered cookie in the error path?
> +
> + inode = new_inode(erofs_pseudo_mnt->mnt_sb);
> + if (!inode) {
> + kfree(ctx->name);
> + return -ENOMEM;
> + }
Ditto.
> +
> + ctx->domain = domain;
> + ctx->anon_inode = inode;
> + inode->i_private = ctx;
> + erofs_fscache_domain_get(domain);
> + *fscache = ctx;
> + return 0;
> +}
> +
> +int erofs_domain_register_cookie(struct super_block *sb,
> + struct erofs_fscache **fscache, char *name, bool need_inode)
> +{
> + int err;
> + struct inode *inode;
> + struct erofs_fscache *ctx;
> + struct erofs_sb_info *sbi = EROFS_SB(sb);
> + struct erofs_domain *domain = sbi->domain;
> + struct super_block *psb = erofs_pseudo_mnt->mnt_sb;
> +
> + mutex_lock(&domain->mutex);
What is domain->mutex used for?
> + list_for_each_entry(inode, &psb->s_inodes, i_sb_list) {
> + ctx = inode->i_private;
> + if (!ctx)
> + continue;
> + if (!strcmp(ctx->name, name)) {
> + *fscache = ctx;
> + igrab(inode);
> + mutex_unlock(&domain->mutex);
> + return 0;
> + }
> + }
> + err = erofs_fscache_domain_init_cookie(sb, fscache, name, need_inode);
> + mutex_unlock(&domain->mutex);
> + return err;
> +}
> diff --git a/fs/erofs/internal.h b/fs/erofs/internal.h
> index 2790c93ffb83..efa4f4ad77cc 100644
> --- a/fs/erofs/internal.h
> +++ b/fs/erofs/internal.h
> @@ -110,6 +110,9 @@ struct erofs_domain {
> struct erofs_fscache {
> struct fscache_cookie *cookie;
> struct inode *inode;
> + struct inode *anon_inode;
Why can't we reuse @inode for anon_inode?
> + struct erofs_domain *domain;
> + char *name;
> };
>
> struct erofs_sb_info {
> @@ -625,6 +628,9 @@ int erofs_fscache_register_domain(struct super_block *sb);
> int erofs_fscache_register_cookie(struct super_block *sb,
> struct erofs_fscache **fscache,
> char *name, bool need_inode);
> +int erofs_domain_register_cookie(struct super_block *sb,
> + struct erofs_fscache **fscache,
> + char *name, bool need_inode);
> void erofs_fscache_unregister_cookie(struct erofs_fscache **fscache);
>
> extern const struct address_space_operations erofs_fscache_access_aops;
> @@ -646,6 +652,12 @@ static inline int erofs_fscache_register_cookie(struct super_block *sb,
> {
> return -EOPNOTSUPP;
> }
> +static inline int erofs_domain_register_cookie(struct super_block *sb,
> + struct erofs_fscache **fscache,
> + char *name, bool need_inode)
> +{
> + return -EOPNOTSUPP;
> +}
>
> static inline void erofs_fscache_unregister_cookie(struct erofs_fscache **fscache)
> {
> diff --git a/fs/erofs/super.c b/fs/erofs/super.c
> index 667a78f0ee70..11c5ba84567c 100644
> --- a/fs/erofs/super.c
> +++ b/fs/erofs/super.c
> @@ -245,8 +245,12 @@ static int erofs_init_device(struct erofs_buf *buf, struct super_block *sb,
> }
>
> if (erofs_is_fscache_mode(sb)) {
> - ret = erofs_fscache_register_cookie(sb, &dif->fscache,
> - dif->path, false);
> + if (sbi->opt.domain_id)
> + ret = erofs_domain_register_cookie(sb, &dif->fscache, dif->path,
> + false);
> + else
> + ret = erofs_fscache_register_cookie(sb, &dif->fscache, dif->path,
> + false);
> if (ret)
> return ret;
> } else {
> @@ -726,6 +730,8 @@ static int erofs_fc_fill_super(struct super_block *sb, struct fs_context *fc)
> err = erofs_fscache_register_domain(sb);
> if (err)
> return err;
> + err = erofs_domain_register_cookie(sb, &sbi->s_fscache,
> + sbi->opt.fsid, true);
> } else {
> err = erofs_fscache_register_fs(sb);
> if (err)
--
Thanks,
Jingbo
next prev parent reply other threads:[~2022-09-13 6:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 10:53 [PATCH V2 0/5] Introduce erofs shared domain Jia Zhu
2022-09-02 10:53 ` [PATCH V2 1/5] erofs: add 'domain_id' mount option for on-demand read sementics Jia Zhu
2022-09-02 10:53 ` [PATCH V2 2/5] erofs: introduce fscache-based domain Jia Zhu
2022-09-09 8:42 ` JeffleXu
2022-09-13 4:31 ` [External] " Jia Zhu
2022-09-13 6:34 ` JeffleXu
2022-09-14 3:02 ` JeffleXu
2022-09-14 3:15 ` [External] " Jia Zhu
2022-09-02 10:53 ` [PATCH V2 3/5] erofs: add 'domain_id' prefix when register sysfs Jia Zhu
2022-09-09 9:23 ` JeffleXu
2022-09-09 9:26 ` JeffleXu
2022-09-13 4:35 ` [External] " Jia Zhu
2022-09-02 10:53 ` [PATCH V2 4/5] erofs: remove duplicated unregister_cookie Jia Zhu
2022-09-09 9:55 ` JeffleXu
2022-09-09 10:28 ` JeffleXu
2022-09-13 4:52 ` [External] " Jia Zhu
2022-09-13 4:37 ` Jia Zhu
2022-09-02 10:53 ` [PATCH V2 5/5] erofs: support fscache based shared domain Jia Zhu
2022-09-13 6:27 ` JeffleXu [this message]
2022-09-13 12:59 ` [External] " Jia Zhu
2022-09-08 6:49 ` [PATCH V2 0/5] Introduce erofs " Jia Zhu
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=097a8ffb-c8b0-ed10-6c82-8a6de9bed09b@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@kernel.org \
--cc=yinxin.x@bytedance.com \
--cc=zhujia.zj@bytedance.com \
/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).