All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] blk-mq: don't call ktime_get_ns() if we don't need it
Date: Fri, 30 Nov 2018 13:54:13 -0700	[thread overview]
Message-ID: <29202974-a205-bd80-298e-52e24dfed48c@kernel.dk> (raw)
In-Reply-To: <2f4b6ca1-23e5-b7fd-286a-e3a76cfc411e@kernel.dk>

On 11/30/18 10:29 AM, Jens Axboe wrote:
> On 11/30/18 10:27 AM, Christoph Hellwig wrote:
>> On Fri, Nov 30, 2018 at 08:56:25AM -0700, Jens Axboe wrote:
>>> We only need the request fields and the end_io time if we have stats
>>> enabled, or if we have a scheduler attached as those may use it for
>>> completion time stats.
>>>
>>> Signed-off-by: Jens Axboe <axboe@kernel.dk>
>>> ---
>>>  block/blk-mq.c | 13 ++++++++++---
>>>  1 file changed, 10 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/block/blk-mq.c b/block/blk-mq.c
>>> index 7dcef565dc0f..2b458e9da946 100644
>>> --- a/block/blk-mq.c
>>> +++ b/block/blk-mq.c
>>> @@ -316,7 +316,8 @@ static struct request *blk_mq_rq_ctx_init(struct blk_mq_alloc_data *data,
>>>  	RB_CLEAR_NODE(&rq->rb_node);
>>>  	rq->rq_disk = NULL;
>>>  	rq->part = NULL;
>>> -	rq->start_time_ns = ktime_get_ns();
>>> +	if (data->q->elevator)
>>> +		rq->start_time_ns = ktime_get_ns();
>>
>> We also seem to use start_time_ns it in blk_account_io_done.
> 
> But only if RQF_STATS is set, in which case we are passing it in correctly.

Oh, needs a stats check for this one, for some reason I was thinking
of the end_io path. Will update.

-- 
Jens Axboe


      reply	other threads:[~2018-11-30 20:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-30 15:56 [PATCH] blk-mq: don't call ktime_get_ns() if we don't need it Jens Axboe
2018-11-30 17:27 ` Christoph Hellwig
2018-11-30 17:29   ` Jens Axboe
2018-11-30 20:54     ` 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=29202974-a205-bd80-298e-52e24dfed48c@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --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 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.