From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC] btrfs: remove cow fixup related code
Date: Mon, 7 Dec 2020 15:56:03 +0100 [thread overview]
Message-ID: <20201207145603.GA6430@twin.jikos.cz> (raw)
In-Reply-To: <20201207071352.106160-1-wqu@suse.com>
On Mon, Dec 07, 2020 at 03:13:52PM +0800, Qu Wenruo wrote:
> >From the initial merge of btrfs, there is always the mystery cow fixup.
For the record, the code needs to stay for because it's still needed.
Though finding the exact point where it happens on intel architectures
is not easy, it's required on s390 because of the separate page bits
tracking at least. How exactly it works and why the code exists is left
as an exercise to the reader.
prev parent reply other threads:[~2020-12-07 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 7:13 [PATCH RFC] btrfs: remove cow fixup related code Qu Wenruo
2020-12-07 14:56 ` David Sterba [this message]
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=20201207145603.GA6430@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=wqu@suse.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