From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: dsterba@suse.cz, torvalds@linux-foundation.org,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 5.20
Date: Tue, 2 Aug 2022 14:32:15 +0200 [thread overview]
Message-ID: <20220802123215.GJ13489@twin.jikos.cz> (raw)
In-Reply-To: <c360943e-c922-9688-5956-e3e5a35c06d8@gmx.com>
On Tue, Aug 02, 2022 at 09:11:09AM +0800, Qu Wenruo wrote:
> On 2022/8/2 00:40, David Sterba wrote:
> > Notable fixes:
> >
> > - raid56
> > - reduce parity writes, skip sectors of stripe when there are no data
> > updates
> > - restore reading from stripe cache instead of triggering new read
>
> Small typo I guess.
> It's the opposite, restore reading from on-disk data instead of using
> stripe cache.
Thanks.
Linus, please replace the sentence with
- restore reading from on-disk data instead of using stripe
cache, this reduces chances to damage correct data due to RMW
cycle
next prev parent reply other threads:[~2022-08-02 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 16:40 [GIT PULL] Btrfs updates for 5.20 David Sterba
2022-08-02 1:11 ` Qu Wenruo
2022-08-02 12:32 ` David Sterba [this message]
2022-08-03 22:29 ` pr-tracker-bot
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=20220802123215.GJ13489@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=torvalds@linux-foundation.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).