linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org
Subject: Re: avoid a few q_usage_counter roundtrips v3
Date: Tue, 19 May 2020 09:43:07 -0600	[thread overview]
Message-ID: <aa30fd0d-e107-f99d-3979-f6e0199f6a61@kernel.dk> (raw)
In-Reply-To: <20200516182801.482930-1-hch@lst.de>

On 5/16/20 12:27 PM, Christoph Hellwig wrote:
> Hi Jens,
> 
> the way we track reference on q_usage_counter is a little weird at the
> moment, in that we often have to grab another reference in addition to
> the current one.  This small series reshuffles that to avoid the extra
> references in the normal I/O path.
> 
> Changes since v2:
>  - increase the q_usage_counter critical section a bit in
>    blk_mq_alloc_request_hctx
> 
> Changes since v1:
>  - rebased to the lastest for-5.8/block tree with the blk-crypt addition

Applied, thanks.

-- 
Jens Axboe


      parent reply	other threads:[~2020-05-19 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 18:27 avoid a few q_usage_counter roundtrips v3 Christoph Hellwig
2020-05-16 18:27 ` [PATCH 1/4] blk-mq: move the call to blk_queue_enter_live out of blk_mq_get_request Christoph Hellwig
2020-05-16 18:27 ` [PATCH 2/4] blk-mq: remove a pointless queue enter pair in blk_mq_alloc_request Christoph Hellwig
2020-05-16 18:28 ` [PATCH 3/4] blk-mq: remove a pointless queue enter pair in blk_mq_alloc_request_hctx Christoph Hellwig
2020-05-16 18:44   ` Bart Van Assche
2020-05-16 18:28 ` [PATCH 4/4] blk-mq: allow blk_mq_make_request to consume the q_usage_counter reference Christoph Hellwig
2020-05-19 15:43 ` 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=aa30fd0d-e107-f99d-3979-f6e0199f6a61@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@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;
as well as URLs for NNTP newsgroup(s).