All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Valente <paolo.valente@linaro.org>
To: sedat.dilek@gmail.com
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
	Jens Axboe <axboe@kernel.dk>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	linux-block@vger.kernel.org, Goldwyn Rodrigues <rgoldwyn@suse.de>,
	Mark Brown <broonie@kernel.org>
Subject: Re: Playing with BFQ
Date: Tue, 16 May 2017 15:41:20 +0200	[thread overview]
Message-ID: <BF9A4309-BFBD-4442-B559-25363A123CD5@linaro.org> (raw)
In-Reply-To: <CA+icZUVionDoiynHpT3i9Lz0UYS0oeU4VZSjCMX3e+PC=u-f_Q@mail.gmail.com>


> Il giorno 16 mag 2017, alle ore 15:38, Sedat Dilek =
<sedat.dilek@gmail.com> ha scritto:
>=20
> [...]
>=20
>>>>> What about those two (Kconfig) patches which is in your current
>>>>> bfq-4.11.y patchset.
>>>>>=20
>>>>=20
>>>> I'm not sure I fully understand the purpose of the two patches you
>>>> propose (in your following emails).  The first patch seems to move =
BFQ
>>>> config options to a different position in Kconfig.iosched, but the
>>>> position of those items should be irrelevant.  Am I missing =
something?
>>>> The second patch seems to have to do with configuration bits of bfq
>>>> for blk, yet such a bfq version is not available in mainline.
>>>>=20
>>>> In any case, for possible new submissions, you should inline your
>>>> patches.  For complete instructions on submitting patches, have a =
look
>>>> at Documentation/process/submitting-patches
>>>>=20
>>>=20
>>> All my testings was done with your patchset against Linux v4.11.y.
>>> You have the same kconfig/kbuild stuff in your 0001 patch [1], so =
:-)?
>>> What you have in 0001 is missing in Linux v4.12-rc1.
>>> Not sure if this is intended.
>>=20
>> 4.12-rc1 contains bfq for blk-mq, while the patch you mention is for
>> bfq for blk (never accepted in mainline).  Maybe you could get a
>> clearer idea by having a look at the commits that add bfq (for =
blk-mq)
>> in 4.12-rc1.
>>=20
>=20
> I recall, Markus pointed me to that difference between the BFQ =
implementations.
> For testing purposes: You want people to test BFQ in Linux v4.12?
>=20

That would be awesome.  For the moment, I would be very happy even if
it just didn't crash!

Thanks,
Paolo

> - Sedat -
>=20
>> Hope this helps,
>> Paolo
>>=20
>>> I will re-submit and add a "4.12" in the subject-line when I am at =
home.
>>>=20
>>> - Sedat -
>>>=20
>>> [1] =
http://algo.ing.unimo.it/people/paolo/disk_sched/patches/4.11.0-v8r11/0001=
-block-cgroups-kconfig-build-bits-for-BFQ-v7r11-4.11..patch
>>=20

      reply	other threads:[~2017-05-16 13:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  7:54 Playing with BFQ Sedat Dilek
2017-05-02  8:00 ` Markus Trippelsdorf
2017-05-02  8:07   ` Sedat Dilek
2017-05-02  9:14     ` Sedat Dilek
2017-05-02 12:07   ` Sedat Dilek
2017-05-02 12:16     ` Markus Trippelsdorf
2017-05-03  8:00       ` Sedat Dilek
2017-05-03  9:16         ` Markus Trippelsdorf
2017-05-03  9:24           ` Paolo Valente
2017-05-13  7:54             ` Sedat Dilek
2017-05-13  8:00               ` Sedat Dilek
2017-05-03  9:21         ` Paolo Valente
2017-05-13  7:50           ` Sedat Dilek
2017-05-16  8:45             ` Paolo Valente
2017-05-16 13:22               ` Sedat Dilek
2017-05-16 13:28                 ` Paolo Valente
2017-05-16 13:38                   ` Sedat Dilek
2017-05-16 13:41                     ` Paolo Valente [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=BF9A4309-BFBD-4442-B559-25363A123CD5@linaro.org \
    --to=paolo.valente@linaro.org \
    --cc=axboe@kernel.dk \
    --cc=broonie@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=rgoldwyn@suse.de \
    --cc=sedat.dilek@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.