From: Christoph Hellwig <hch@infradead.org>
To: Naohiro Aota <naohiro.aota@wdc.com>
Cc: linux-btrfs@vger.kernel.org, hch@infradead.org,
josef@toxicpanda.com, dsterba@suse.cz
Subject: Re: [PATCH v2 02/10] btrfs: zoned: introduce block_group context to btrfs_eb_write_context
Date: Tue, 1 Aug 2023 00:55:26 -0700 [thread overview]
Message-ID: <ZMi6bhTOP1Bmdw2A@infradead.org> (raw)
In-Reply-To: <31cfb11cd71edc3513f0d65d1da6a2b6d3b959e7.1690823282.git.naohiro.aota@wdc.com>
> struct btrfs_eb_write_context ctx = {
> .wbc = wbc,
> .eb = NULL,
> + .block_group = NULL,
Same comment as for the last patch.
Otherwise looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2023-08-01 7:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 17:17 [PATCH v2 00/10] btrfs: zoned: write-time activation of metadata block group Naohiro Aota
2023-07-31 17:17 ` [PATCH v2 01/10] btrfs: introduce struct to consolidate extent buffer write context Naohiro Aota
2023-08-01 7:53 ` Christoph Hellwig
2023-08-01 11:59 ` Johannes Thumshirn
2023-07-31 17:17 ` [PATCH v2 02/10] btrfs: zoned: introduce block_group context to btrfs_eb_write_context Naohiro Aota
2023-08-01 7:55 ` Christoph Hellwig [this message]
2023-08-01 12:05 ` Johannes Thumshirn
2023-07-31 17:17 ` [PATCH v2 03/10] btrfs: zoned: return int from btrfs_check_meta_write_pointer Naohiro Aota
2023-08-01 7:56 ` Christoph Hellwig
2023-08-01 12:07 ` Johannes Thumshirn
2023-08-02 0:20 ` Naohiro Aota
2023-07-31 17:17 ` [PATCH v2 04/10] btrfs: zoned: defer advancing meta_write_pointer Naohiro Aota
2023-08-01 7:58 ` Christoph Hellwig
2023-08-02 1:35 ` Naohiro Aota
2023-08-01 12:13 ` Johannes Thumshirn
2023-07-31 17:17 ` [PATCH v2 05/10] btrfs: zoned: update meta_write_pointer on zone finish Naohiro Aota
2023-08-01 12:15 ` Johannes Thumshirn
2023-07-31 17:17 ` [PATCH v2 06/10] btrfs: zoned: reserve zones for an active metadata/system block group Naohiro Aota
2023-08-01 12:23 ` Johannes Thumshirn
2023-08-02 4:50 ` Naohiro Aota
2023-07-31 17:17 ` [PATCH v2 07/10] btrfs: zoned: activate metadata block group on write time Naohiro Aota
2023-07-31 17:17 ` [PATCH v2 08/10] btrfs: zoned: no longer count fresh BG region as zone unusable Naohiro Aota
2023-07-31 17:17 ` [PATCH v2 09/10] btrfs: zoned: don't activate non-DATA BG on allocation Naohiro Aota
2023-08-01 12:34 ` Johannes Thumshirn
2023-07-31 17:17 ` [PATCH v2 10/10] btrfs: zoned: re-enable metadata over-commit for zoned mode Naohiro Aota
2023-08-01 12:35 ` Johannes Thumshirn
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=ZMi6bhTOP1Bmdw2A@infradead.org \
--to=hch@infradead.org \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=naohiro.aota@wdc.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