From: Christoph Hellwig <hch@infradead.org>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH v3 0/4] btrfs: basic refactor of btrfs_buffered_write()
Date: Tue, 25 Aug 2020 12:44:32 +0100 [thread overview]
Message-ID: <20200825114432.GA2873@infradead.org> (raw)
In-Reply-To: <20200825054808.16241-1-wqu@suse.com>
Does much refactoring of this code make sense? Goldwyn has initial
patches to convert the buffered I/O path to iomap, and I hope that would
pick up speed now that the direct I/O conversion landed.
next prev parent reply other threads:[~2020-08-25 11:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 5:48 [PATCH v3 0/4] btrfs: basic refactor of btrfs_buffered_write() Qu Wenruo
2020-08-25 5:48 ` [PATCH v3 1/4] btrfs: refactor @nrptrs calculation " Qu Wenruo
2020-08-25 5:48 ` [PATCH v3 2/4] btrfs: refactor btrfs_buffered_write() into process_one_batch() Qu Wenruo
2020-08-25 5:48 ` [PATCH v3 3/4] btrfs: remove the again: tag in process_one_batch() Qu Wenruo
2020-08-25 5:48 ` [PATCH v3 4/4] btrfs: avoid allocating unnecessary page pointers Qu Wenruo
2020-08-25 7:46 ` kernel test robot
2020-08-25 7:46 ` kernel test robot
2020-08-25 7:57 ` kernel test robot
2020-08-25 7:57 ` kernel test robot
2020-08-26 12:31 ` kernel test robot
2020-08-26 12:31 ` kernel test robot
2020-08-27 8:56 ` [LTP] [btrfs] a73ab37eba: last_state.is_incomplete_run kernel test robot
2020-08-27 8:56 ` kernel test robot
2020-08-27 8:56 ` kernel test robot
2020-08-25 11:44 ` Christoph Hellwig [this message]
2020-08-25 13:32 ` [PATCH v3 0/4] btrfs: basic refactor of btrfs_buffered_write() Goldwyn Rodrigues
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=20200825114432.GA2873@infradead.org \
--to=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=rgoldwyn@suse.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.