linux-kernel - Re: [PATCH] make blk_mq_map_queues more friendly for cpu topology

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]

Date:   Wed, 27 Mar 2019 17:39:16 +0800
From:   Dongli Zhang <dongli.zhang@...cle.com>
To:     luferry <luferry@....com>
Cc:     Christoph Hellwig <hch@....de>, Jens Axboe <axboe@...nel.dk>,
        Ming Lei <ming.lei@...hat.com>, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] make blk_mq_map_queues more friendly for cpu topology

On 03/27/2019 05:17 PM, luferry wrote:
> 
> 
> 
> Actually,  I just bought one vm from public cloud provider and run into this problem.
> after reading code and compare pci device info, I reproduce this scenario.

There is lack of vector issue when number of queues is more than maxcpus as well.

https://lore.kernel.org/lkml/e4afe4c5-0262-4500-aeec-60f30734b4fc@default

I was going to send out patch to fix that specific case on virtio side.

BTW, is your VM's virtio mmio based or pci based?

As mentioned in previous email, when I was playing with firecracker by amazon,
the virtio-blk is mmio based. Not sure if that would lead to the lack of vector
issue.

Dongli Zhang