linux-kernel - Re: [PATCH RFC] x86 / CPU: Add cpu isolation flag for avoiding disturbance from aperfmperf IPI

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: <8b54ebf5-7daf-2760-7210-e0e945014c9e@yandex-team.ru>
Date:   Thu, 25 Apr 2019 15:27:12 +0300
From:   Konstantin Khlebnikov <khlebnikov@...dex-team.ru>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     linux-kernel@...r.kernel.org, Len Brown <len.brown@...el.com>,
        Frederic Weisbecker <frederic@...nel.org>,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        Ingo Molnar <mingo@...hat.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCH RFC] x86 / CPU: Add cpu isolation flag for avoiding
 disturbance from aperfmperf IPI

On 25.04.2019 14:45, Peter Zijlstra wrote:
> On Thu, Apr 25, 2019 at 01:46:51PM +0300, Konstantin Khlebnikov wrote:
>> Sensitive workloads like DPDK polling do not like any interrupts.
>>
>> This patch adds flag 'freq' for boot option 'isolcpu': isolcpu=freq,<cpus>.
>>
>> Users like show_cpuinfo() fallback to frequency from generic cpufreq
>> policy if arch-specific requesting method returns 0.
> 
> Then don't touch that sysfs file?

What sysfs file?
I mean many applications read /proc/cpuinfo and this triggers IPI to all cpus.

> 
> I really hate having an option for just this.
> 

This could be generalized to 'isolate cpu from unnecessary IPI'.
Something like mm pagevec drain also could be avoided.