Re: [PATCH 3/8] blk-mq: avoid to write intermediate result to hctx->next_cpu

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Ming Lei <ming.lei@xxxxxxxxxx>
Subject: Re: [PATCH 3/8] blk-mq: avoid to write intermediate result to hctx->next_cpu
From: Christoph Hellwig <hch@xxxxxx>
Date: Mon, 9 Apr 2018 12:05:17 +0200
Cc: Jens Axboe <axboe@xxxxxxxxx>, linux-block@xxxxxxxxxxxxxxx, Christian Borntraeger <borntraeger@xxxxxxxxxx>, Stefan Haberland <sth@xxxxxxxxxxxxxxxxxx>
In-reply-to: <20180408094814.28953-4-ming.lei@redhat.com>
User-agent: Mutt/1.5.17 (2007-11-01)

On Sun, Apr 08, 2018 at 05:48:09PM +0800, Ming Lei wrote:
> This patch figures out the final selected CPU, then writes
> it to hctx->next_cpu once, then we can avoid to intermediate
> next cpu observed from other dispatch paths.

Looks good,

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

References:
- [PATCH 0/8] blk-mq: fix and improve queue mapping
  - From: Ming Lei
- [PATCH 3/8] blk-mq: avoid to write intermediate result to hctx->next_cpu
  - From: Ming Lei

Prev by Date: Re: [PATCH 2/8] blk-mq: don't keep offline CPUs mapped to hctx 0
Next by Date: Re: [PATCH 4/8] blk-mq: introduce blk_mq_hw_queue_first_cpu() to figure out first cpu
Previous by thread: [PATCH 3/8] blk-mq: avoid to write intermediate result to hctx->next_cpu
Next by thread: Re: [PATCH 3/8] blk-mq: avoid to write intermediate result to hctx->next_cpu
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux