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] [day] [month] [year] [list]
Message-ID: <TY2PR06MB3424577F435AF6EBFBDB6260855D9@TY2PR06MB3424.apcprd06.prod.outlook.com>
Date:   Wed, 5 Oct 2022 02:20:50 +0000
From:   Angus Chen <angus.chen@...uarmicro.com>
To:     Jason Wang <jasowang@...hat.com>
CC:     "mst@...hat.com" <mst@...hat.com>,
        "virtualization@...ts.linux-foundation.org" 
        <virtualization@...ts.linux-foundation.org>,
        "linux-kernel@...r.kernel.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.
This patch is just prevent the device
which have no intx support to request INTX.
It can be occur when msix is out of memory or out of irq 
Capability etc.
So could you pls help to review this patch first?

Thank you.
> 
> Thanks
> 
> >

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ