Date: Tue, 13 Dec 2016 08:17:39 -0700
From: Jens Axboe <axboe@fb.com>
To: Paolo Valente <paolo.valente@linaro.org>
CC: <linux-block@vger.kernel.org>,
        Linux-Kernal <linux-kernel@vger.kernel.org>, <osandov@fb.com>
Subject: Re: [PATCHSET/RFC v2] blk-mq scheduling framework
Message-ID: <20161213151739.GA32618@kernel.dk>
References: <1481228005-9245-1-git-send-email-axboe@fb.com>
 <9D1F7CB5-4043-448B-A553-D6A9804D5089@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9D1F7CB5-4043-448B-A553-D6A9804D5089@linaro.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1550
Lines: 39

On Tue, Dec 13 2016, Paolo Valente wrote:
> 
> > Il giorno 08 dic 2016, alle ore 21:13, Jens Axboe <axboe@fb.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!

No worries, ask away if you have questions. As you might have seen, it's
still a little bit of a moving target, but it's getting closer every
day. I'll post a v3 later today hopefully that will be a good fix point
for you. I'll need to add the io context setup etc, that's not there
yet, as only cfq/bfq uses that.

-- 
Jens Axboe