From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v4 0/9] btrfs: compression: refactor and enhancement preparing for subpage compression support
Date: Tue, 22 Jun 2021 14:41:19 +0200 [thread overview]
Message-ID: <20210622124119.GI28158@twin.jikos.cz> (raw)
In-Reply-To: <ae3df571-4eeb-d046-6a90-ac67158d4067@gmx.com>
On Tue, Jun 22, 2021 at 07:50:38PM +0800, Qu Wenruo wrote:
> On 2021/6/22 下午7:14, David Sterba wrote:
> > On Fri, Jun 18, 2021 at 06:46:51AM +0800, Qu Wenruo wrote:
> Although the biggest challenge for testing is the hardware.
>
> I guess even with subpage merged into upstream in v5.14, it won't really
> get many tests from real world, unlike x86_64 that every guys in the
> mail list is testing on.
>
> Although we have cheap ARM SoC boards in recent days, there aren't
> really much good candidates for us to utilize.
>
> Either they don't have fast enough CPUs (2x 2GHz+ A72 or more) or don't
> have even a single PCIe lane for NVME, or don't have good enough
> upstream kernel support.
>
> So far RPI CM4 would be a pretty good candidate, and I'm already using
> it, but without overclocking and good heatsink, its CPU can be a little
> bit slow, and the PCIe2.0 x1 lane is far from enough.
>
> But I totally understand how difficult it could be for even kernel
> developers to setup all the small things up.
>
> Like TTY, libvirt, edk2 firmware for VM, RPI specific boot sequence etc.
>
> Thus even subpage get merged, I still think we need way more rounds of
> upstream release to really get some feedback.
Back in January I got a hold of a decent arm64 machine and tested the 64K
build in a VM, the hardware should be good enough for running at least
3 in parallel and I think there were more identical physical machines
available so we can use that for testing once all the prep work is done.
Right now all people involved know that the subpage support may be buggy
or incomplete so we can rely on external testing for some time.
prev parent reply other threads:[~2021-06-22 12:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 5:14 [PATCH v4 0/9] btrfs: compression: refactor and enhancement preparing for subpage compression support Qu Wenruo
2021-06-17 5:14 ` [PATCH v4 1/9] btrfs: remove a dead comment for btrfs_decompress_bio() Qu Wenruo
2021-06-17 5:14 ` [PATCH v4 2/9] btrfs: introduce compressed_bio::pending_sectors to trace compressed bio more elegantly Qu Wenruo
2021-06-18 4:16 ` Anand Jain
2021-06-18 5:18 ` Qu Wenruo
2021-06-17 5:14 ` [PATCH v4 3/9] btrfs: handle errors properly inside btrfs_submit_compressed_read() Qu Wenruo
2021-06-17 5:14 ` [PATCH v4 4/9] btrfs: handle errors properly inside btrfs_submit_compressed_write() Qu Wenruo
2021-06-17 5:14 ` [PATCH v4 5/9] btrfs: introduce submit_compressed_bio() for compression Qu Wenruo
2021-06-17 5:14 ` [PATCH v4 6/9] btrfs: introduce alloc_compressed_bio() " Qu Wenruo
2021-06-17 5:14 ` [PATCH v4 7/9] btrfs: make btrfs_submit_compressed_read() to determine stripe boundary at bio allocation time Qu Wenruo
2021-06-17 5:14 ` [PATCH v4 8/9] btrfs: make btrfs_submit_compressed_write() " Qu Wenruo
2021-06-17 5:14 ` [PATCH v4 9/9] btrfs: remove unused function btrfs_bio_fits_in_stripe() Qu Wenruo
2021-06-17 16:47 ` [PATCH v4 0/9] btrfs: compression: refactor and enhancement preparing for subpage compression support David Sterba
2021-06-17 22:46 ` Qu Wenruo
2021-06-22 11:14 ` David Sterba
2021-06-22 11:50 ` Qu Wenruo
2021-06-22 12:41 ` David Sterba [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=20210622124119.GI28158@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.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 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.