From: Wang Yugui <wangyugui@e16-tech.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs read_ahead_kb 4096 is too big? or any tuning/design guide
Date: Sun, 12 Feb 2023 20:50:55 +0800 [thread overview]
Message-ID: <20230212205054.8863.409509F4@e16-tech.com> (raw)
Hi,
btrfs read_ahead_kb 4096 is too big?
or is there any tuning/design guide?
As a compare,
read_ahead_kb of block device is 128
read_ahead_kb of xfs filesystem is 128
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2023/02/12
reply other threads:[~2023-02-12 12:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230212205054.8863.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--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