From: Jens Axboe <axboe@kernel.dk>
To: Shaohua Li <shli@fb.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Cc: bhelgaas@google.com, hch@lst.de
Subject: Re: [PATCH V2 1/3] blk-mq: allocate blk_mq_tags and requests in correct node
Date: Fri, 24 Feb 2017 15:23:50 -0700 [thread overview]
Message-ID: <fa1eaadf-db72-a642-a917-3f633af2ca55@kernel.dk> (raw)
In-Reply-To: <b41e8f74-007d-c818-4915-3ea3b7c229b5@fb.com>
On 02/01/2017 12:09 PM, Jens Axboe wrote:
> On 02/01/2017 09:53 AM, Shaohua Li wrote:
>> blk_mq_tags/requests of specific hardware queue are mostly used in
>> specific cpus, which might not be in the same numa node as disk. For
>> example, a nvme card is in node 0. half hardware queue will be used by
>> node 0, the other node 1.
>
> All three patches look good to me. Bjorn, to avoid complications, if
> you can review/ack patch #2, then I will queue it up through the block
> tree for 4.11.
Bjorn, ping. You were CC'ed on the original patch three weeks ago.
--
Jens Axboe
next prev parent reply other threads:[~2017-02-24 22:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 17:53 [PATCH V2 1/3] blk-mq: allocate blk_mq_tags and requests in correct node Shaohua Li
2017-02-01 17:53 ` [PATCH V2 2/3] PCI: add an API to get node from vector Shaohua Li
2017-02-01 18:11 ` Christoph Hellwig
2017-02-24 22:29 ` Bjorn Helgaas
2017-02-24 22:34 ` Jens Axboe
2017-02-01 17:53 ` [PATCH V2 3/3] nvme: allocate nvme_queue in correct node Shaohua Li
2017-02-01 18:14 ` Christoph Hellwig
2017-02-01 18:11 ` [PATCH V2 1/3] blk-mq: allocate blk_mq_tags and requests " Christoph Hellwig
2017-02-01 19:09 ` Jens Axboe
2017-02-24 22:23 ` Jens Axboe [this message]
2017-02-24 22:30 ` Bjorn Helgaas
2017-02-25 2:54 ` Jens Axboe
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=fa1eaadf-db72-a642-a917-3f633af2ca55@kernel.dk \
--to=axboe@kernel.dk \
--cc=bhelgaas@google.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shli@fb.com \
/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