From: Christoph Hellwig <hch@infradead.org>
To: Dimitrios Apostolou <jimis@gmx.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: (PING) btrfs sequential 8K read()s from compressed files are not merging
Date: Wed, 26 Jul 2023 05:54:29 -0700 [thread overview]
Message-ID: <ZMEXhfDG2BinQEOy@infradead.org> (raw)
In-Reply-To: <fd0bbbc3-4a42-3472-dc6e-5a1cb51df10e@gmx.net>
FYI, I can reproduce similar findings to yours. I'm somewhere between
dealing with regressions and travel and don't actually have time to
fully root cause it.
The most likely scenario is probably some interaction between the read
ahead window that is based around the actual I/O size, and the btrfs
compressed extent design that always compressed a fixed sized chunk
of data.
next prev parent reply other threads:[~2023-07-26 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 18:56 btrfs sequential 8K read()s from compressed files are not merging Dimitrios Apostolou
2023-07-17 14:11 ` Dimitrios Apostolou
2023-07-26 10:59 ` (PING) " Dimitrios Apostolou
2023-07-26 12:54 ` Christoph Hellwig [this message]
2023-07-26 13:44 ` Dimitrios Apostolou
2023-08-29 13:02 ` Dimitrios Apostolou
2023-08-30 11:54 ` Qu Wenruo
2023-08-30 18:18 ` Dimitrios Apostolou
2023-08-31 0:22 ` Anand Jain
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=ZMEXhfDG2BinQEOy@infradead.org \
--to=hch@infradead.org \
--cc=jimis@gmx.net \
--cc=linux-btrfs@vger.kernel.org \
/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).