linux-kernel - Re: [PATCH V2 1/3] blk-mq: allocate blk_mq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fa1eaadf-db72-a642-a917-3f633af2ca55@kernel.dk>
Date:   Fri, 24 Feb 2017 15:23:50 -0700
From:   Jens Axboe <axboe@...nel.dk>
To:     Shaohua Li <shli@...com>, linux-kernel@...r.kernel.org,
        linux-block@...r.kernel.org
Cc:     bhelgaas@...gle.com, hch@....de
Subject: Re: [PATCH V2 1/3] blk-mq: allocate blk_mq_tags and requests in
 correct node

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