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: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	ulf.hansson@linaro.org, broonie@kernel.org, jeremywh7@gmail.com,
	lnicola@dend.ro
Subject: Re: [PATCH BUGFIX/IMPROVEMENT 0/2] doc, block, bfq: improve documentation on how to to properly configure bfq
Date: Thu, 31 Aug 2017 13:55:45 -0600	[thread overview]
Message-ID: <56db9c20-ecc6-eefb-6e64-302118cad49c@kernel.dk> (raw)
In-Reply-To: <20170831180031.3747-1-paolo.valente@linaro.org>

On 08/31/2017 12:00 PM, Paolo Valente wrote:
> Many users have reported the lack of an HOWTO for properly configuring
> bfq as a function of the goal one wants to achieve (max
> responsiveness, max throughput, ...). The second patch in this
> two-patch series addresses this issue by improving the file
> bfq-iosched.txt in such a way that it also provides some guidance on
> this task. The first patch fixes some issues that I have found while
> working on the file.

Applied for 4.14, thanks Paolo.

-- 
Jens Axboe

      parent reply	other threads:[~2017-08-31 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 18:00 [PATCH BUGFIX/IMPROVEMENT 0/2] doc, block, bfq: improve documentation on how to to properly configure bfq Paolo Valente
2017-08-31 18:00 ` [PATCH BUGFIX/IMPROVEMENT 1/2] doc, block, bfq: fix some typos and remove stale stuff Paolo Valente
2017-08-31 18:00 ` [PATCH BUGFIX/IMPROVEMENT 2/2] doc, block, bfq: better describe how to properly configure bfq Paolo Valente
2017-08-31 19:55 ` 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=56db9c20-ecc6-eefb-6e64-302118cad49c@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=broonie@kernel.org \
    --cc=jeremywh7@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lnicola@dend.ro \
    --cc=paolo.valente@linaro.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