linux-kernel - Re: [PATCH 10/13] blk-mq: provide a default queue mapping for PCI device

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:   Mon, 19 Sep 2016 15:49:32 +0200
From:   Christoph Hellwig <hch@....de>
To:     Alexander Gordeev <agordeev@...hat.com>
Cc:     Christoph Hellwig <hch@....de>, axboe@...com, tglx@...utronix.de,
        keith.busch@...el.com, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 10/13] blk-mq: provide a default queue mapping for PCI
        device

On Mon, Sep 19, 2016 at 09:33:14AM +0200, Alexander Gordeev wrote:
> Considering this code is to be used by any device - an assumption
> that queue number and interrupt vector are always equal seems
> questionable. I.e. what about non-contiguous MSI-Xs?

It's just a generic default - see the discussion with Jens in the
intro mail for the thread for anyother example that can't be handled
easily.  If we get enough devices for a given scheme we can add another
common helper, in the worst case we'll need driver code for the scheme.