linux-kernel - Re: [PATCH] nvme: use the correct msix vector for each queue

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20161207230516.GB25959@localhost.localdomain>
Date:   Wed, 7 Dec 2016 18:05:16 -0500
From:   Keith Busch <keith.busch@...el.com>
To:     Dan Streetman <ddstreet@...e.org>
Cc:     Jens Axboe <axboe@...com>, linux-nvme@...ts.infradead.org,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Dan Streetman <dan.streetman@...onical.com>
Subject: Re: [PATCH] nvme: use the correct msix vector for each queue

On Wed, Dec 07, 2016 at 05:46:34PM -0500, Dan Streetman wrote:
> 
> Is there a reason you want to share the interrupt between the queues?

The admin queue is hardly ever used (if at all) compared to an IO queue's
usage, so why waste the resource? I bet you can't measure a preformance
difference on queues that don't share, and it's reasonable to expect an
nvme controller's MSI-x count matches the IO queue count, which forces
us to share a vector.