[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL7ro1G59CGj99YKJYAP=8W+sejE+q=XqXtYjmiXXP9=xVcjwA@mail.gmail.com>
Date: Mon, 6 Feb 2023 16:31:22 +0100
From: Alexander Larsson <alexl@...hat.com>
To: Gao Xiang <hsiangkao@...ux.alibaba.com>
Cc: Amir Goldstein <amir73il@...il.com>,
Miklos Szeredi <miklos@...redi.hu>,
Jingbo Xu <jefflexu@...ux.alibaba.com>, gscrivan@...hat.com,
brauner@...nel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, david@...morbit.com,
viro@...iv.linux.org.uk, Vivek Goyal <vgoyal@...hat.com>,
Josef Bacik <josef@...icpanda.com>
Subject: Re: [PATCH v3 0/6] Composefs: an opportunistically sharing verified
image filesystem
On Mon, Feb 6, 2023 at 2:27 PM Gao Xiang <hsiangkao@...ux.alibaba.com> wrote:
> On 2023/2/6 20:43, Alexander Larsson wrote:
> >
> > One problem I ran into is that erofs seems to only support mounting
> > filesystem images that are created with the native page size. This
> > means I can't mount a erofs image created on a 4k page-size machine on
> > an arm64 mac with 64k pages. That doesn't seem great. Maybe this
> > limitation can be lifted from the erofs code though.
>
> Honestly, EROFS 64k support has been in our roadmap for a quite long
> time, and it has been almost done for the uncompressed part apart from
> replacing EROFS_BLKSIZ to erofs_blksiz(sb).
Good, as long as it is on the roadmap.
> Currently it's not urgent just because our Cloud environment always use
> 4k PAGE_SIZE, but it seems Android will consider 16k pagesize as well, so
> yes, we will support !4k page size for the uncompressed part in the near
> future. But it seems that arm64 RHEL 9 switched back to 4k page size?
Honestly I'm not following it all that closely, but I think Fedora was
at least talking about 64k pages.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Alexander Larsson Red Hat, Inc
alexl@...hat.com alexander.larsson@...il.com
Powered by blists - more mailing lists