Return-Path: Received: from mail.linutronix.de (146.0.238.70:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 23 Jan 2019 01:39:28 -0000 Received: from mga17.intel.com ([192.55.52.151]) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1gm7Vn-0006gv-4E for speck@linutronix.de; Wed, 23 Jan 2019 02:39:27 +0100 Date: Tue, 22 Jan 2019 17:39:23 -0800 From: Andi Kleen Subject: [MODERATED] Re: [PATCH v5 22/27] MDSv5 24 Message-ID: <20190123013923.GY6118@tassilo.jf.intel.com> References: <5fc3209d2880402d332ec93cf076467b3706a401.1547858934.git.ak@linux.intel.com> <20190122012233.GS6118@tassilo.jf.intel.com> <20190122175614.GV6118@tassilo.jf.intel.com> MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit To: speck@linutronix.de List-ID: On Tue, Jan 22, 2019 at 07:56:20PM +0100, speck for Thomas Gleixner wrote: > On Tue, 22 Jan 2019, speck for Andi Kleen wrote: > > On Tue, Jan 22, 2019 at 05:09:05PM +0100, speck for Thomas Gleixner wrote: > > At least in my limited testing the patch doesn't cause that > > actually, even though it may be counterintuitive. > > > > See the numbers for Chrome for example in the last EBPF patch. That's > > a complex workload with many context switches, and it gets > > a clear roughly every third syscall > > I'd rather see numbers with the switch_to hackery actually using > thread_info::flags. Not sure what you mean here? It's using thread_info flags. > > > So this only leaves some latency sensitive workloads, > > which cannot mitigate interrupts, but the interrupt handlers for those can > > be fixed over time based on profiling results. Overall I suspect it > > will be only a small subset of the total number of drivers. > > Ah, and who is going to that analysis and who is going to fix that? People who care about performance will notice it. If they don't it's probably not that important. -Andi