From: Wang Yugui <wangyugui@e16-tech.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs write-bandwidth performance regression of 6.5-rc4/rc3
Date: Tue, 01 Aug 2023 17:32:13 +0800 [thread overview]
Message-ID: <20230801173208.4F08.409509F4@e16-tech.com> (raw)
In-Reply-To: <20230801090316.GA25781@lst.de>
Hi,
> On Tue, Aug 01, 2023 at 04:56:58PM +0800, Wang Yugui wrote:
> > > Odd. What CPU are you using to test? It seems like it doesn't set
> > > BTRFS_FS_CSUM_IMPL_FAST as that is the only way to even hit a potential
> > > difference. Or are you using a non-standard checksum type?
> >
> > The CPU is E5 2680 v2.
>
> Is this in a VM and not passing through cpu flags? What does dmesg
> say when mounting? Norally it should say something like:
>
> [ 23.461448] BTRFS info (device vdb): using crc32c (crc32c-intel) checksum algorithm
This is NOT VM.
dmesg output:
[ 250.596544] raid6: skipped pq benchmark and selected sse2x4
[ 250.602836] raid6: using ssse3x2 recovery algorithm
[ 250.612812] xor: automatically using best checksumming function avx
[ 250.895573] Btrfs loaded, assert=on, zoned=yes, fsverity=no
[ 250.905249] BTRFS: device fsid f5ebfdd6-6bf6-4c2b-b47b-79517bc00c8f devid 3 transid 6 /dev/nvme3n1 scanned by systemd-udevd (1726)
[ 250.922155] BTRFS: device fsid f5ebfdd6-6bf6-4c2b-b47b-79517bc00c8f devid 4 transid 6 /dev/nvme0n1 scanned by systemd-udevd (1729)
[ 250.935965] BTRFS: device fsid f5ebfdd6-6bf6-4c2b-b47b-79517bc00c8f devid 1 transid 6 /dev/nvme1n1 scanned by systemd-udevd (1724)
[ 250.968268] BTRFS: device fsid f5ebfdd6-6bf6-4c2b-b47b-79517bc00c8f devid 2 transid 6 /dev/nvme2n1 scanned by systemd-udevd (1723)
[ 251.070139] BTRFS info (device nvme1n1): using crc32c (crc32c-intel) checksum algorithm
[ 251.079164] BTRFS info (device nvme1n1): using free space tree
[ 251.089871] BTRFS info (device nvme1n1): enabling ssd optimizations
[ 251.096921] BTRFS info (device nvme1n1): auto enabling async discard
[ 251.104417] BTRFS info (device nvme1n1): checking UUID tree
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2023/08/01
next prev parent reply other threads:[~2023-08-01 9:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 7:22 btrfs write-bandwidth performance regression of 6.5-rc4/rc3 Wang Yugui
2023-08-01 2:22 ` Wang Yugui
2023-08-01 8:35 ` Christoph Hellwig
2023-08-01 8:56 ` Wang Yugui
2023-08-01 9:03 ` Christoph Hellwig
2023-08-01 9:32 ` Wang Yugui [this message]
2023-08-01 10:00 ` Christoph Hellwig
2023-08-01 13:04 ` Wang Yugui
2023-08-01 14:59 ` Christoph Hellwig
2023-08-01 15:51 ` Wang Yugui
2023-08-01 15:56 ` Christoph Hellwig
2023-08-01 15:57 ` Christoph Hellwig
2023-08-02 0:04 ` Wang Yugui
2023-08-02 9:26 ` Christoph Hellwig
2023-08-11 8:58 ` Linux regression tracking (Thorsten Leemhuis)
2023-08-11 10:31 ` Christoph Hellwig
2023-08-11 14:23 ` Wang Yugui
2023-08-11 14:52 ` Chris Mason
2023-08-13 9:50 ` Wang Yugui
2023-08-29 9:45 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-11 7:02 ` Thorsten Leemhuis
2023-09-11 23:20 ` Wang Yugui
2023-09-12 7:58 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-26 10:55 ` Thorsten Leemhuis
2023-09-26 17:18 ` Chris Mason
2023-09-27 11:30 ` Linux regression tracking (Thorsten Leemhuis)
2023-12-06 14:22 ` Linux regression tracking (Thorsten Leemhuis)
2023-12-13 15:57 ` Naohiro Aota
2023-08-02 8:45 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=20230801173208.4F08.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=hch@lst.de \
--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