linux-kernel - RE: [Patch v4] genirq/matrix: Choose CPU for managed IRQs based on how many of them are allocated

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: <DM5PR21MB018511C3ABE491AFC768D3E4CECB0@DM5PR21MB0185.namprd21.prod.outlook.com>
Date:   Tue, 6 Nov 2018 23:01:48 +0000
From:   Long Li <longli@...rosoft.com>
To:     Thomas Gleixner <tglx@...utronix.de>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [Patch v4] genirq/matrix: Choose CPU for managed IRQs based on
 how many of them are allocated

> Subject: Re: [Patch v4] genirq/matrix: Choose CPU for managed IRQs based
> on how many of them are allocated
> 
> Long,
> 
> On Tue, 6 Nov 2018, Long Li wrote:
> 
> > From: Long Li <longli@...rosoft.com>
> >
> > On a large system with multiple devices of the same class (e.g. NVMe
> > disks, using managed IRQs), the kernel tends to concentrate their IRQs
> > on several CPUs.
> 
> Thanks for addressing the comments. Well done.
> 
> I've merged it, but took the liberty to rework the changelog so all the
> background information which we exchanged over the various iterations is
> preserved there.

Thank you!

Long

> 
> Thanks,
> 
> 	tglx