public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: axboe@kernel.dk, josef@toxicpanda.com, hch@lst.de
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET block/for-next] blkcg: Improve blkg config helpers and make iolatency init lazy
Date: Thu, 5 Jan 2023 08:56:23 -1000	[thread overview]
Message-ID: <Y7cdV0vlExjtkF6C@slm.duckdns.org> (raw)
In-Reply-To: <20230105002007.157497-1-tj@kernel.org>

On Wed, Jan 04, 2023 at 02:20:03PM -1000, Tejun Heo wrote:
> Hello,
> 
> * Improve blkg config helpers so that they can be used consistently for all
>   the existing use cases. This also allows keeps using the same bdev open
>   instance across lazy init of rq_qos policies.
> 
> * Update iolatency so that it initializes lazily when a latency target is
>   set for the first time. This avoids registering the rq_qos policy when
>   iolatency is not used which removes unnecessary calls into iolat from IO
>   hot paths.

I forgot to update bfq. Will post v2 soon.

Thanks.

-- 
tejun

      parent reply	other threads:[~2023-01-05 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05  0:20 [PATCHSET block/for-next] blkcg: Improve blkg config helpers and make iolatency init lazy Tejun Heo
2023-01-05  0:20 ` [PATCH 1/4] blkcg: Drop unnecessary RCU read [un]locks from blkg_conf_prep/finish() Tejun Heo
2023-01-05  0:20 ` [PATCH 2/4] blkcg: Restructure blkg_conf_prep() and friends Tejun Heo
2023-01-05  0:20 ` [PATCH 3/4] blk-iolatency: s/blkcg_rq_qos/iolat_rq_qos/ Tejun Heo
2023-01-05  0:20 ` [PATCH 4/4] blk-iolatency: Make initialization lazy Tejun Heo
2023-01-05 18:56 ` Tejun Heo [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=Y7cdV0vlExjtkF6C@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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