linux-kernel - Re: [PATCHSET/RFC v2] blk-mq scheduling framework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <9D1F7CB5-4043-448B-A553-D6A9804D5089@linaro.org>
Date:   Tue, 13 Dec 2016 10:26:28 +0100
From:   Paolo Valente <paolo.valente@...aro.org>
To:     Jens Axboe <axboe@...com>
Cc:     Jens Axboe <axboe@...nel.dk>, linux-block@...r.kernel.org,
        Linux-Kernal <linux-kernel@...r.kernel.org>, osandov@...com
Subject: Re: [PATCHSET/RFC v2] blk-mq scheduling framework


> Il giorno 08 dic 2016, alle ore 21:13, Jens Axboe <axboe@...com> ha scritto:
> 
> As a followup to this posting from yesterday:
> 
> https://marc.info/?l=linux-block&m=148115232806065&w=2
> 
> this is version 2. I wanted to post a new one fairly quickly, as there
> ended up being a number of potential crashes in v1. This one should be
> solid, I've run mq-deadline on both NVMe and regular rotating storage,
> and we handle the various merging cases correctly.
> 
> You can download it from git as well:
> 
> git://git.kernel.dk/linux-block blk-mq-sched.2
> 
> Note that this is based on for-4.10/block, which is in turn based on
> v4.9-rc1. I suggest pulling it into my for-next branch, which would
> then merge nicely with 'master' as well.
> 

Hi Jens,
this is just to tell you that I have finished running some extensive
tests on this patch series (throughput, responsiveness, low latency
for soft real time).  No regression w.r.t. blk detected, and no
crashes or other anomalies.

Starting to work on BFQ port.  Please be patient with my little
expertise on mq environment, and with my next silly questions!

Thanks,
Paolo


> Changes since v1:
> 
> - Add Kconfig entries to allow the user to choose what the default
>  scheduler should be for blk-mq, and whether that depends on the
>  number of hardware queues.
> 
> - Properly abstract the whole get/put of a request, so we can manage
>  the life time properly.
> 
> - Enable full merging on mq-deadline (front/back, bio-to-rq, rq-to-rq).
>  Has full feature parity with deadline now.
> 
> - Export necessary symbols for compiling mq-deadline as a module.
> 
> - Various API adjustments for the mq schedulers.
> 
> - Various cleanups and improvements.
> 
> - Fix a lot of bugs. A lot. Upgrade!
> 
> block/Kconfig.iosched    |   37 ++
> block/Makefile           |    3 
> block/blk-core.c         |    9 
> block/blk-exec.c         |    3 
> block/blk-flush.c        |    7 
> block/blk-merge.c        |    3 
> block/blk-mq-sched.c     |  265 +++++++++++++++++++
> block/blk-mq-sched.h     |  188 +++++++++++++
> block/blk-mq-tag.c       |    1 
> block/blk-mq.c           |  254 ++++++++++--------
> block/blk-mq.h           |   35 +-
> block/elevator.c         |  194 ++++++++++----
> block/mq-deadline.c      |  647 +++++++++++++++++++++++++++++++++++++++++++++++
> drivers/nvme/host/pci.c  |    1 
> include/linux/blk-mq.h   |    4 
> include/linux/elevator.h |   34 ++
> 16 files changed, 1495 insertions(+), 190 deletions(-)
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-block" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html