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, huyue2@coolpad.com,
linux-kernel@vger.kernel.org, yinxin.x@bytedance.com
Subject: Re: [External] Re: [PATCH V2 2/5] erofs: introduce fscache-based domain
Date: Tue, 13 Sep 2022 14:34:46 +0800 [thread overview]
Message-ID: <b9794188-f1e1-20ab-6aec-04312cbb02bf@linux.alibaba.com> (raw)
In-Reply-To: <fe9199a2-a8d5-98c9-461b-e7a2cbf87516@bytedance.com>
On 9/13/22 12:31 PM, Jia Zhu wrote:
>
>
> 在 2022/9/9 16:42, JeffleXu 写道:
>>> int erofs_fscache_register_cookie(struct super_block *sb,
>>> struct erofs_fscache **fscache,
>>> char *name, bool need_inode)
>>> @@ -495,7 +581,8 @@ int erofs_fscache_register_fs(struct super_block
>>> *sb)
>>> char *name;
>>> int ret = 0;
>>> - name = kasprintf(GFP_KERNEL, "erofs,%s", sbi->opt.fsid);
>>> + name = kasprintf(GFP_KERNEL, "erofs,%s",
>>> + sbi->domain ? sbi->domain->domain_id : sbi->opt.fsid);
>>
>> Do we also need to encode the cookie name in the "<domain_id>,<fsid>"
>> format? This will affect the path of the cache files.
>>
> I think even though the cookies have the same name, they belong to
> different volumes(path). Cookies do not affect each other.
> Are there other benefits to doing so?
Okay. The current implementation is correct. Please ignore the noise.
--
Thanks,
Jingbo
next prev parent reply other threads:[~2022-09-13 6:34 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 [this message]
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
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=b9794188-f1e1-20ab-6aec-04312cbb02bf@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).