From: NeilBrown <nfbrown@novell.com>
To: Joey Liao <joeyliao@qnap.com>, linux-raid@vger.kernel.org
Subject: Re: Why does raid0 set max_hw_sectors as chunk size but the other raid types doesn't?
Date: Thu, 02 Jun 2016 14:38:29 +1000 [thread overview]
Message-ID: <87lh2op5mi.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <CAHvN=in80JrXO=tDyxNhq9d_wW1ZCCioENyTLu9tYuYYDof20w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2027 bytes --]
On Mon, May 30 2016, Joey Liao wrote:
> Hi,
>
> I have no idea why does raid0_run() in raid0.c use
> blk_queue_max_hw_sectors() to set max_hw_sectors as the chunk size,
> but the other raid types doesn't?
git is your friend.... admittedly you need the 'history' git tree to go
back before 2.6.12, but it is available.
http://git.kernel.org/cgit/linux/kernel/git/history/history.git/commit/?id=f556ef000efc90a45a285f4f0b4fd70bb70f
>
> What's the purpose to limit the max_hw_sectors in raid0?
unfortunately the commit doesn't answer that question. I think it was
to ensure requests larger than one chunk were not created. If they were
they would just have to be split, so there is no much to gain.
>
> Is it related to the source code logic issue or the performance issue?
>
> Besides, I have an interesting observation. If I remove all the
> following queue limitation codes in raid0_run() of raid0.c, the block
> size in iostat is still the same as chunk size even the input block
> size is much larger than the chunk size. Why???
Because when you write to a RAID0 you *must* divide each request up into
chunk-sizes sub-requests, and send them to different devices.
NeilBrown
>
> - blk_queue_max_hw_sectors(mddev->queue, mddev->chunk_sectors);
> - blk_queue_max_write_same_sectors(mddev->queue, mddev->chunk_sectors);
> + //blk_queue_max_hw_sectors(mddev->queue, mddev->chunk_sectors);
> + //blk_queue_max_write_same_sectors(mddev->queue, mddev->chunk_sectors);
>
> - blk_queue_io_min(mddev->queue, mddev->chunk_sectors << 9);
> - blk_queue_io_opt(mddev->queue,
> - (mddev->chunk_sectors << 9) * mddev->raid_disks);
> + //blk_queue_io_min(mddev->queue, mddev->chunk_sectors << 9);
> + /*blk_queue_io_opt(mddev->queue,
> + (mddev->chunk_sectors << 9) * mddev->raid_disks);*/
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-06-02 4:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 11:55 Why does raid0 set max_hw_sectors as chunk size but the other raid types doesn't? Joey Liao
2016-06-02 4:38 ` NeilBrown [this message]
2016-06-02 9:30 ` Joey Liao
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=87lh2op5mi.fsf@notabene.neil.brown.name \
--to=nfbrown@novell.com \
--cc=joeyliao@qnap.com \
--cc=linux-raid@vger.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;
as well as URLs for NNTP newsgroup(s).