From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: Naohiro Aota <Naohiro.Aota@wdc.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"wangyugui@e16-tech.com" <wangyugui@e16-tech.com>,
"clm@meta.com" <clm@meta.com>, "hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH v2] btrfs: introduce sync_csum_mode to tweak sync checksum behavior
Date: Wed, 31 Jan 2024 19:58:43 +0100 [thread overview]
Message-ID: <20240131185843.GR31555@twin.jikos.cz> (raw)
In-Reply-To: <9624d589-43ff-40c6-81af-2c7b577edb22@wdc.com>
On Wed, Jan 31, 2024 at 02:15:32PM +0000, Johannes Thumshirn wrote:
> On 31.01.24 08:15, Naohiro Aota wrote:
> > We disable offloading checksum to workqueues and do it synchronously when
> > the checksum algorithm is fast. However, as reported in the link below,
> > RAID0 with multiple devices may suffer from the sync checksum, because
> > "fast checksum" is still not fast enough to catch up RAID0 writing.
> >
> > To measure the effectiveness of sync checksum for developers, it would be
> > better to have a switch for the sync checksum under CONFIG_BTRFS_DEBUG
> > hood.
> >
> > This commit introduces fs_devices->sync_csum_mode for CONFIG_BTRFS_DEBUG,
> > so that a btrfs developer can change the behavior by writing to
> > /sys/fs/btrfs/<uuid>/sync_csum. The default is "auto" which is the same as
> > the previous behavior. Or, you can set "on" or "off" to always/never use
> > sync checksum.
> >
> > More benchmark should be collected with this knob to implement a proper
> > criteria to enable/disable sync checksum.
> >
> > Link: https://lore.kernel.org/linux-btrfs/20230731152223.4EFB.409509F4@e16-tech.com/
> > Link: https://lore.kernel.org/linux-btrfs/p3vo3g7pqn664mhmdhlotu5dzcna6vjtcoc2hb2lsgo2fwct7k@xzaxclba5tae/
> > Signed-off-by: Naohiro Aota <naohiro.aota@wdc.com>
>
> As access to sysfs and fs_info can happen concurrently, should the
> read/write of fs_devices->sync_csum_mode be guarded by a
> READ_ONCE()/WRITE_ONCE()?
Yes we use the *_ONCE helpers for values set from sysfs in cases where
it's without bad effects to race and change the value in the middle.
Here it would only skip one checksum offload/sync. It's not really a
guard but a note that there's something special about the value.
next prev parent reply other threads:[~2024-01-31 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 7:13 [PATCH v2] btrfs: introduce sync_csum_mode to tweak sync checksum behavior Naohiro Aota
2024-01-31 14:15 ` Johannes Thumshirn
2024-01-31 18:58 ` David Sterba [this message]
2024-02-01 1:16 ` Naohiro Aota
2024-02-01 2:11 ` David Sterba
2024-01-31 19:04 ` David Sterba
2024-02-01 1:28 ` Naohiro Aota
2024-02-01 2:14 ` David Sterba
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=20240131185843.GR31555@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=Johannes.Thumshirn@wdc.com \
--cc=Naohiro.Aota@wdc.com \
--cc=clm@meta.com \
--cc=hch@lst.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangyugui@e16-tech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox