linux-kernel - Re: [PATCH v3 00/11] smp: cross CPU call interface

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: <YoS2q9a1o123hIGi@infradead.org>
Date:   Wed, 18 May 2022 02:04:43 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Donghai Qiao <dqiao@...hat.com>
Cc:     akpm@...ux-foundation.org, sfr@...b.auug.org.au, arnd@...db.de,
        peterz@...radead.org, heying24@...wei.com,
        andriy.shevchenko@...ux.intel.com, axboe@...nel.dk,
        rdunlap@...radead.org, tglx@...utronix.de, gor@...ux.ibm.com,
        donghai.w.qiao@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 00/11] smp: cross CPU call interface

I still haven't seen any good rationale for this.  It causes massive
churn just to have more complicated interface (and thus more code)
than before.  What is the benefit?

I'm also not sure what is formal about this interface, or why it
should be formal.  IPIs should be rare, and we'd better off looking
for instances we can remove entirely.