public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Tejun Heo <tj@kernel.org>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	ulf.hansson@linaro.org, linus.walleij@linaro.org,
	broonie@kernel.org
Subject: Re: [WIP PATCHSET 0/4] WIP branch for bfq-mq
Date: Mon, 13 Feb 2017 15:29:35 -0700	[thread overview]
Message-ID: <0425b6c7-d6be-b019-e750-bf858e864307@kernel.dk> (raw)
In-Reply-To: <478A4EBE-9218-4527-9F8A-42AAEBDC9470@linaro.org>

On 02/13/2017 02:09 PM, Paolo Valente wrote:
> 
>> Il giorno 07 feb 2017, alle ore 18:24, Paolo Valente <paolo.valente@linaro.org> ha scritto:
>>
>> Hi,
>>
>> I have finally pushed here [1] the current WIP branch of bfq for
>> blk-mq, which I have tentatively named bfq-mq.
>>
>> This branch *IS NOT* meant for merging into mainline and contain code
>> that mau easily violate code style, and not only, in many
>> places. Commits implement the following main steps:
>> 1) Add the last version of bfq for blk
>> 2) Clone bfq source files into identical bfq-mq source files
>> 3) Modify bfq-mq files to get a working version of bfq for blk-mq
>> (cgroups support not yet functional)
>>
>> In my intentions, the main goals of this branch are:
>>
>> 1) Show, as soon as I could, the changes I made to let bfq-mq comply
>> with blk-mq-sched framework. I though this could be particularly
>> useful for Jens, being BFQ identical to CFQ in terms of hook
>> interfaces and io-context handling, and almost identical in terms
>> request-merging.
>>
>> 2) Enable people to test this first version bfq-mq. Code is purposely
>> overfull of log messages and invariant checks that halt the system on
>> failure (lock assertions, BUG_ONs, ...).
>>
>> To make it easier to revise commits, I'm sending the patches that
>> transform bfq into bfq-mq (last four patches in the branch [1]). They
>> work on two files, bfq-mq-iosched.c and bfq-mq.h, which, at the
>> beginning, are just copies of bfq-iosched.c and bfq.h.
>>
> 
> Hi,
> this is just to inform that, as I just wrote to Bart, I have rebase
> the branch [1] against the current content of for-4.11/next.
> 
> Jens, Omar, did you find the time to have a look at the main commits
> or to run some test?

I only looked at the core change you proposed for passing in the
bio as well, and Omar fixed up the icq exit part and I also applied
that patch. I haven't look at any of the bfq-mq patches at all yet.
Not sure what I can do with those, I don't think those are
particularly useful to anyone but you.

Might make more sense to post the conversion for review as a
whole.

-- 
Jens Axboe

      reply	other threads:[~2017-02-13 22:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 17:24 [WIP PATCHSET 0/4] WIP branch for bfq-mq Paolo Valente
2017-02-07 17:24 ` [WIP PATCHSET 1/4] blk-mq: pass bio to blk_mq_sched_get_rq_priv Paolo Valente
2017-02-10 16:10   ` Jens Axboe
2017-02-07 17:24 ` [WIP PATCHSET 2/4] Move thinktime from bic to bfqq Paolo Valente
2017-02-07 17:24 ` [WIP PATCHSET 3/4] Embed bfq-ioc.c and add locking on request queue Paolo Valente
2017-02-07 17:24 ` [WIP PATCHSET 4/4] Modify interface and operation to comply with blk-mq-sched Paolo Valente
2017-02-10 16:08 ` [WIP PATCHSET 0/4] WIP branch for bfq-mq Bart Van Assche
2017-02-10 16:49   ` Paolo Valente
2017-02-10 16:45 ` Bart Van Assche
2017-02-10 16:49   ` Paolo Valente
2017-02-10 18:13     ` Bart Van Assche
2017-02-10 19:49       ` Paolo Valente
2017-02-13 21:07         ` Paolo Valente
2017-02-13 22:07           ` Bart Van Assche
2017-02-13 22:38             ` Bart Van Assche
2017-02-22 21:29               ` Paolo Valente
2017-02-24 18:44                 ` Bart Van Assche
2017-02-25 17:45                   ` Paolo Valente
2017-02-10 18:34 ` Bart Van Assche
2017-02-10 19:33   ` Paolo Valente
2017-02-13 21:09 ` Paolo Valente
2017-02-13 22:29   ` Jens Axboe [this message]

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=0425b6c7-d6be-b019-e750-bf858e864307@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=broonie@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.valente@linaro.org \
    --cc=tj@kernel.org \
    --cc=ulf.hansson@linaro.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