From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Liu Bo <bo.liu@linux.alibaba.com>
Cc: Yan Song <imeoer@linux.alibaba.com>,
LKML <linux-kernel@vger.kernel.org>,
Peng Tao <tao.peng@linux.alibaba.com>,
Joseph Qi <joseph.qi@linux.alibaba.com>,
Changwei Ge <chge@linux.alibaba.com>,
Liu Jiang <gerry@linux.alibaba.com>,
linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH v3 1/2] erofs: decouple basic mount options from fs_context
Date: Thu, 7 Oct 2021 14:29:16 +0800 [thread overview]
Message-ID: <YV6TvAPGYOMGxenU@B-P7TQMD6M-0146.local> (raw)
In-Reply-To: <20211007061048.GA84859@rsjd01523.et2sqa>
Hi Bo,
On Thu, Oct 07, 2021 at 02:10:48PM +0800, Liu Bo wrote:
> On Thu, Oct 07, 2021 at 03:44:52AM +0800, Gao Xiang wrote:
> > Previously, EROFS mount options are all in the basic types, so
> > erofs_fs_context can be directly copied with assignment. However,
> > when the multiple device feature is introduced, it's hard to handle
> > multiple device information like the other basic mount options.
> >
> > There is no need to allocate the whole sb info in advance, instead,
> > let's separate the basic mount options from fs_context, thus
> > multiple device information can be handled gracefully then.
>
> This is a bit confusing, IIRC, currently erofs does not allocate the whole
> sb info in advance, does it?
No, it doesn't. I just mentioned there are 2 ways to pass fs private
contexts to fs_context:
1) allocate sbi in advance by using fc->s_fs_info;
2) allocate/pass a fs private fs_context by using fc->fs_private;
erofs uses the second way.... Actually I'm fine with getting rid of
such expression to avoid confusion for the next version...
Thanks,
Gao Xiang
>
> thanks,
> liubo
prev parent reply other threads:[~2021-10-07 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 19:44 [PATCH v3 1/2] erofs: decouple basic mount options from fs_context Gao Xiang
2021-10-06 19:44 ` [PATCH v3 2/2] erofs: add multiple device support Gao Xiang
2021-10-07 6:42 ` Liu Bo
2021-10-07 6:10 ` [PATCH v3 1/2] erofs: decouple basic mount options from fs_context Liu Bo
2021-10-07 6:29 ` Gao Xiang [this message]
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=YV6TvAPGYOMGxenU@B-P7TQMD6M-0146.local \
--to=hsiangkao@linux.alibaba.com \
--cc=bo.liu@linux.alibaba.com \
--cc=chge@linux.alibaba.com \
--cc=gerry@linux.alibaba.com \
--cc=imeoer@linux.alibaba.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tao.peng@linux.alibaba.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).