From: Jens Axboe <axboe@kernel.dk>
To: Junxiao Bi <junxiao.bi@oracle.com>
Cc: andi@lisas.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] block: make nr_requests tunable for loop
Date: Mon, 09 Jun 2014 20:41:33 -0600 [thread overview]
Message-ID: <5396705D.5020507@kernel.dk> (raw)
In-Reply-To: <1402367460-5305-1-git-send-email-junxiao.bi@oracle.com>
On 2014-06-09 20:31, Junxiao Bi wrote:
> commit 7b5a3522 (loop: Limit the number of requests in the bio list) limit
> the request number in loop queue to not over 128. Since the "request_fn" of
> loop device is null, the requests number is not allowed tuned. Make it tunable
> from sysfs can improve performance.
>
> The following test is done on a machine with 512M memory. The backend of
> /dev/loop1 is a nfs file.
>
> [root@bijx mnt]# cat /sys/block/loop0/queue/nr_requests
> 128
> [root@bijx mnt]# dd if=/dev/zero of=/dev/loop0 bs=1M count=5000
> 5000+0 records in
> 5000+0 records out
> 5242880000 bytes (5.2 GB) copied, 501.572 s, 10.5 MB/s
> [root@bijx mnt]#
> [root@bijx mnt]# echo 1024 > /sys/block/loop0/queue/nr_requests
> [root@bijx mnt]# cat /sys/block/loop0/queue/nr_requests
> 1024
> [root@bijx mnt]# dd if=/dev/zero of=/dev/loop0 bs=1M count=5000
> 5000+0 records in
> 5000+0 records out
> 5242880000 bytes (5.2 GB) copied, 464.481 s, 11.3 MB/s
>
> Signed-off-by: Junxiao Bi <junxiao.bi@oracle.com>
> ---
> block/blk-core.c | 6 ++++++
> block/blk-sysfs.c | 9 +++------
> 2 files changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/block/blk-core.c b/block/blk-core.c
> index 40d6548..58c4bd4 100644
> --- a/block/blk-core.c
> +++ b/block/blk-core.c
> @@ -851,6 +851,12 @@ int blk_update_nr_requests(struct request_queue *q, unsigned int nr)
> q->nr_requests = nr;
> blk_queue_congestion_threshold(q);
>
> + /* for loop device, return after set its nr_requests */
> + if (!q->request_fn) {
> + spin_unlock_irq(q->queue_lock);
> + return 0;
> + }
It'd be prettier to split this differently - something ala:
if (request_fn)
blk_update_congestion_thresholds(q);
But I think you have a larger issue here... For the request lists, we
update the congestion thresholds and wakeup anyone waiting, if we need
to. There's no way to do that for loop, since the waitqueue is internal
to loop.
--
Jens Axboe
next prev parent reply other threads:[~2014-06-10 2:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 2:31 [PATCH V2] block: make nr_requests tunable for loop Junxiao Bi
2014-06-10 2:41 ` Jens Axboe [this message]
2014-06-10 2:50 ` Junxiao Bi
2014-06-10 3:12 ` Jens Axboe
2014-06-10 3:29 ` Junxiao Bi
2014-06-11 2:40 ` Junxiao Bi
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=5396705D.5020507@kernel.dk \
--to=axboe@kernel.dk \
--cc=andi@lisas.de \
--cc=junxiao.bi@oracle.com \
--cc=linux-kernel@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