linux-kernel - Re: [PATCH v3] virtio_pci: avoid to request intx irq if pin is zero

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: <CACGkMEtaMRifeDDDk3kb7QY-1mO1V2t6PFjgRXwRoN8NbRaD=A@mail.gmail.com>
Date:   Thu, 29 Sep 2022 10:30:33 +0800
From:   Jason Wang <jasowang@...hat.com>
To:     Angus Chen <angus.chen@...uarmicro.com>
Cc:     mst@...hat.com, virtualization@...ts.linux-foundation.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] virtio_pci: avoid to request intx irq if pin is zero

On Wed, Sep 28, 2022 at 6:47 PM Angus Chen <angus.chen@...uarmicro.com> wrote:
>
> The background is that we use dpu in cloud computing,the arch is x86,80
> cores.We will have a lots of virtio devices,like 512 or more.
> When we probe about 200 virtio_blk devices,it will fail and
> the stack is print as follows:

Not for this patch, but I wonder if it's time to introduce per cpu
virtio interrupts instead of per device ones? This may help in this
case.

Thanks

>