From: Qu Wenruo <wqu@suse.com> To: Michael Ellerman <mpe@ellerman.id.au>, Qu Wenruo <quwenruo.btrfs@gmx.com>, Neal Gompa <ngompa13@gmail.com> Cc: Christophe Leroy <christophe.leroy@csgroup.eu>, Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>, David Sterba <dsterba@suse.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, linuxppc-dev@lists.ozlabs.org, Btrfs BTRFS <linux-btrfs@vger.kernel.org>, linux-hexagon@vger.kernel.org, Hector Martin <marcan@marcan.st> Subject: Re: [PATCH] fs: btrfs: Disable BTRFS on platforms having 256K pages Date: Fri, 7 Jan 2022 13:21:53 +0800 [thread overview] Message-ID: <7fc839d7-c13d-d658-5247-62540d76e7c0@suse.com> (raw) In-Reply-To: <87bl0o2lgo.fsf@mpe.ellerman.id.au> On 2022/1/7 12:55, Michael Ellerman wrote: > Qu Wenruo <quwenruo.btrfs@gmx.com> writes: >> On 2022/1/7 00:31, Neal Gompa wrote: >>> On Wed, Jan 5, 2022 at 7:05 AM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote: >>>> >>>> Hi Christophe, >>>> >>>> I'm recently enhancing the subpage support for btrfs, and my current >>>> branch should solve the problem for btrfs to support larger page sizes. >>>> >>>> But unfortunately my current test environment can only provide page size >>>> with 64K or 4K, no 16K or 128K/256K support. >>>> >>>> Mind to test my new branch on 128K page size systems? >>>> (256K page size support is still lacking though, which will be addressed >>>> in the future) >>>> >>>> https://github.com/adam900710/linux/tree/metadata_subpage_switch >>>> >>> >>> The Linux Asahi folks have a 16K page environment (M1 Macs)... >> >> Su Yue kindly helped me testing 16K page size, and it's pretty OK there. >> >> So I'm not that concerned. >> >> It's 128K page size that I'm a little concerned, and I have not machine >> supporting that large page size to do the test. > > Did Christophe say he had a 128K system to test on? > > In mainline powerpc only supports 4K/16K/64K/256K. > > AFAIK there's no arch with 128K page size support, but that's only based > on some grepping, maybe it's hidden somewhere. My bad, I thought there would be 128K since there is 256K and 64K support, but that's totally wrong. I'll get PPC guys informed when the 256K page size problem is solved, and then ask for your help. Thanks, Qu > > cheers >
WARNING: multiple messages have this Message-ID (diff)
From: Qu Wenruo <wqu@suse.com> To: Michael Ellerman <mpe@ellerman.id.au>, Qu Wenruo <quwenruo.btrfs@gmx.com>, Neal Gompa <ngompa13@gmail.com> Cc: linux-hexagon@vger.kernel.org, Hector Martin <marcan@marcan.st>, Josef Bacik <josef@toxicpanda.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>, linuxppc-dev@lists.ozlabs.org, Btrfs BTRFS <linux-btrfs@vger.kernel.org> Subject: Re: [PATCH] fs: btrfs: Disable BTRFS on platforms having 256K pages Date: Fri, 7 Jan 2022 13:21:53 +0800 [thread overview] Message-ID: <7fc839d7-c13d-d658-5247-62540d76e7c0@suse.com> (raw) In-Reply-To: <87bl0o2lgo.fsf@mpe.ellerman.id.au> On 2022/1/7 12:55, Michael Ellerman wrote: > Qu Wenruo <quwenruo.btrfs@gmx.com> writes: >> On 2022/1/7 00:31, Neal Gompa wrote: >>> On Wed, Jan 5, 2022 at 7:05 AM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote: >>>> >>>> Hi Christophe, >>>> >>>> I'm recently enhancing the subpage support for btrfs, and my current >>>> branch should solve the problem for btrfs to support larger page sizes. >>>> >>>> But unfortunately my current test environment can only provide page size >>>> with 64K or 4K, no 16K or 128K/256K support. >>>> >>>> Mind to test my new branch on 128K page size systems? >>>> (256K page size support is still lacking though, which will be addressed >>>> in the future) >>>> >>>> https://github.com/adam900710/linux/tree/metadata_subpage_switch >>>> >>> >>> The Linux Asahi folks have a 16K page environment (M1 Macs)... >> >> Su Yue kindly helped me testing 16K page size, and it's pretty OK there. >> >> So I'm not that concerned. >> >> It's 128K page size that I'm a little concerned, and I have not machine >> supporting that large page size to do the test. > > Did Christophe say he had a 128K system to test on? > > In mainline powerpc only supports 4K/16K/64K/256K. > > AFAIK there's no arch with 128K page size support, but that's only based > on some grepping, maybe it's hidden somewhere. My bad, I thought there would be 128K since there is 256K and 64K support, but that's totally wrong. I'll get PPC guys informed when the 256K page size problem is solved, and then ask for your help. Thanks, Qu > > cheers >
next prev parent reply other threads:[~2022-01-07 5:22 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-10 5:23 [PATCH] fs: btrfs: Disable BTRFS on platforms having 256K pages Christophe Leroy 2021-06-10 5:23 ` Christophe Leroy 2021-06-10 13:54 ` [PATCH] " Chris Mason 2021-06-10 13:54 ` Chris Mason 2021-06-10 14:50 ` Christophe Leroy 2021-06-10 14:50 ` Christophe Leroy 2021-06-10 16:20 ` David Sterba 2021-06-10 16:20 ` David Sterba 2021-06-11 12:58 ` Chris Mason 2021-06-11 12:58 ` Chris Mason 2021-06-11 13:21 ` David Sterba 2021-06-11 13:21 ` David Sterba 2021-06-11 16:56 ` Chris Mason 2021-06-11 16:56 ` Chris Mason 2021-06-12 14:44 ` Brian Cain 2021-06-12 14:44 ` Brian Cain 2021-06-11 12:34 ` [PATCH] fs: " David Sterba 2021-06-11 12:34 ` David Sterba 2021-06-11 13:47 ` Qu Wenruo 2021-06-11 13:47 ` Qu Wenruo 2022-01-04 23:32 ` Qu Wenruo 2022-01-04 23:32 ` Qu Wenruo 2022-01-06 16:31 ` Neal Gompa 2022-01-06 16:31 ` Neal Gompa 2022-01-07 0:13 ` Qu Wenruo 2022-01-07 0:13 ` Qu Wenruo 2022-01-07 2:45 ` Hector Martin 2022-01-07 2:45 ` Hector Martin 2022-01-07 4:55 ` Michael Ellerman 2022-01-07 4:55 ` Michael Ellerman 2022-01-07 5:21 ` Qu Wenruo [this message] 2022-01-07 5:21 ` Qu Wenruo 2022-01-10 8:29 ` Christophe Leroy 2022-01-10 8:29 ` Christophe Leroy
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=7fc839d7-c13d-d658-5247-62540d76e7c0@suse.com \ --to=wqu@suse.com \ --cc=christophe.leroy@csgroup.eu \ --cc=clm@fb.com \ --cc=dsterba@suse.com \ --cc=josef@toxicpanda.com \ --cc=linux-btrfs@vger.kernel.org \ --cc=linux-hexagon@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=marcan@marcan.st \ --cc=mpe@ellerman.id.au \ --cc=ngompa13@gmail.com \ --cc=quwenruo.btrfs@gmx.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.