From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>,
linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org
Cc: linux-raid@vger.kernel.org, Song Liu <song@kernel.org>,
Dmitry Monakhov <dmtrmonakhov@yandex-team.ru>
Subject: Re: [PATCH] block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices
Date: Mon, 2 Mar 2020 11:41:28 +0100 [thread overview]
Message-ID: <35ef813c-d5a4-8eb8-073d-9c5814266299@molgen.mpg.de> (raw)
In-Reply-To: <158290150891.4423.13566449569964563258.stgit@buzz>
[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]
Dear Konstantin,
Thank you for the patch.
On 2020-02-28 15:51, Konstantin Khlebnikov wrote:
> Field bdi->io_pages added in commit 9491ae4aade6 ("mm: don't cap request
> size based on read-ahead setting") removes unneeded split of read requests.
>
> Stacked drivers do not call blk_queue_max_hw_sectors(). Instead they setup
The verb is spelled with a space *set up*.
> limits of their devices by blk_set_stacking_limits() + disk_stack_limits().
> Field bio->io_pages stays zero until user set max_sectors_kb via sysfs.
>
> This patch updates io_pages after merging limits in disk_stack_limits().
>
> Commit c6d6e9b0f6b4 ("dm: do not allow readahead to limit IO size") fixed
> the same problem for device-mapper devices, this one fixes MD RAIDs.
Add a Fixes: tag?
Fixes: 9491ae4aade6 ("mm: don't cap request size based on read-ahead setting")
> Signed-off-by: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
> ---
> block/blk-settings.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/block/blk-settings.c b/block/blk-settings.c
> index c8eda2e7b91e..66c45fd79545 100644
> --- a/block/blk-settings.c
> +++ b/block/blk-settings.c
> @@ -664,6 +664,8 @@ void disk_stack_limits(struct gendisk *disk, struct block_device *bdev,
> printk(KERN_NOTICE "%s: Warning: Device %s is misaligned\n",
> top, bottom);
> }
> +
> + t->backing_dev_info->io_pages = t->limits.max_sectors >> (PAGE_SHIFT-9);
> }
> EXPORT_SYMBOL(disk_stack_limits);
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Kind regards,
Paul
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2020-03-02 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 14:51 [PATCH] block: keep bdi->io_pages in sync with max_sectors_kb for stacked devices Konstantin Khlebnikov
2020-03-02 10:41 ` Paul Menzel [this message]
2020-03-02 10:51 ` Konstantin Khlebnikov
2020-03-02 12:16 ` Bob Liu
2020-03-10 21:40 ` Song Liu
2020-03-12 13:40 ` Jens Axboe
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=35ef813c-d5a4-8eb8-073d-9c5814266299@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=axboe@kernel.dk \
--cc=dmtrmonakhov@yandex-team.ru \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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