From: Guoqing Jiang <jgq516@gmail.com>
To: Artur Paszkiewicz <artur.paszkiewicz@intel.com>, song@kernel.org
Cc: linux-raid@vger.kernel.org, Guoqing Jiang <jiangguoqing@kylinos.cn>
Subject: Re: [PATCH 2/5] md: the latest try for improve io stats accounting
Date: Wed, 19 May 2021 09:30:03 +0800 [thread overview]
Message-ID: <2bfe7f2b-5b5b-634d-3996-3c4ed77e74ff@gmail.com> (raw)
In-Reply-To: <2887bc44-dd0b-0b24-ee97-b0a95f0c4936@intel.com>
On 5/18/21 6:12 PM, Artur Paszkiewicz wrote:
> On 18.05.2021 07:32, Guoqing Jiang wrote:
>> + /*
>> + * We don't clone bio for multipath, raid1 and raid10 since we can reuse
>> + * their clone infrastructure.
>> + */
>> + if (blk_queue_io_stat(bio->bi_bdev->bd_disk->queue) &&
>> + (bio->bi_pool != &mddev->md_io_bs) &&
>> + (mddev->level != 1) && (mddev->level != 10) &&
>> + (mddev->level != LEVEL_MULTIPATH)) {
> Maybe add a flag to struct md_personality and check it here? Something
> that will be set only for the personalities which clone the bio
> themselves.
Good point.
> Doesn't this need to check the bio->bi_pool also against mddev->bio_set
> to skip the bios split by md? Similarly to the check against
> bio_chain_endio which you did before.
Hmm, raid0 allocates split bio from mddev->bio_set, but raid5 is
different, it splits bio from r5conf->bio_split. So either let raid5 also
splits bio from mddev->bio_set, or add an additional checking for
raid5. Thoughts?
Thanks,
Guoqing
next prev parent reply other threads:[~2021-05-19 1:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 5:32 [PATCH 0/5] md: io stats accounting Guoqing Jiang
2021-05-18 5:32 ` [PATCH 1/5] md: revert " Guoqing Jiang
2021-05-18 5:32 ` [PATCH 2/5] md: the latest try for improve " Guoqing Jiang
2021-05-18 10:12 ` Artur Paszkiewicz
2021-05-19 1:30 ` Guoqing Jiang [this message]
2021-05-19 7:26 ` Artur Paszkiewicz
2021-05-19 7:46 ` Christoph Hellwig
2021-05-19 8:09 ` Guoqing Jiang
2021-05-20 0:45 ` Song Liu
2021-05-18 13:35 ` Christoph Hellwig
2021-05-19 1:40 ` Guoqing Jiang
2021-05-18 5:32 ` [PATCH 3/5] md-multipath: enable io accounting Guoqing Jiang
2021-05-18 13:37 ` Christoph Hellwig
2021-05-19 1:46 ` Guoqing Jiang
2021-05-18 5:32 ` [PATCH 4/5] md/raid1: " Guoqing Jiang
2021-05-18 13:40 ` Christoph Hellwig
2021-05-19 1:47 ` Guoqing Jiang
2021-05-18 5:32 ` [PATCH 5/5] md/raid10: " Guoqing Jiang
2021-05-19 0:14 ` [PATCH 0/5] md: io stats accounting Song Liu
2021-05-19 1:50 ` Guoqing Jiang
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=2bfe7f2b-5b5b-634d-3996-3c4ed77e74ff@gmail.com \
--to=jgq516@gmail.com \
--cc=artur.paszkiewicz@intel.com \
--cc=jiangguoqing@kylinos.cn \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.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