From: Christoph Hellwig <hch@lst.de>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Christoph Hellwig <hch@lst.de>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org,
Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Subject: Re: [PATCH] btrfs: don't merge pages into bio if their page offset is not continuous
Date: Sat, 13 Aug 2022 09:46:11 +0200 [thread overview]
Message-ID: <20220813074611.GA11755@lst.de> (raw)
In-Reply-To: <1f71de8a-2292-054e-913b-15e41b409de6@gmx.com>
On Sat, Aug 13, 2022 at 03:43:49PM +0800, Qu Wenruo wrote:
> BTW, I'll also update the commit message to mention some future
> cleanups, as now a btrfs_bio is completely a continous range, thus
> things like endio_readpage_release_extent() related infrastructure can
> also be removed.
Yes, there is a lot of things that can be cleaned up with this. For
that reason along I was planning to look into a change like this
eventually, but I should have done it earlier..
prev parent reply other threads:[~2022-08-13 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 7:28 [PATCH] btrfs: don't merge pages into bio if their page offset is not continuous Qu Wenruo
2022-08-13 7:39 ` Christoph Hellwig
2022-08-13 7:43 ` Qu Wenruo
2022-08-13 7:46 ` Christoph Hellwig [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=20220813074611.GA11755@lst.de \
--to=hch@lst.de \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.