Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp5316744imm; Tue, 18 Sep 2018 07:42:18 -0700 (PDT) X-Google-Smtp-Source: ANB0VdYyXY4mXmjS2REaigRcPVdeb/vc5/YqZMgyxZXVoCJ6Z8fTciPoTObrDtWdQUNs0FXLIyDV X-Received: by 2002:a62:280a:: with SMTP id o10-v6mr31128495pfo.129.1537281738723; Tue, 18 Sep 2018 07:42:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537281738; cv=none; d=google.com; s=arc-20160816; b=SF7HWa8WcEDOi8alIlRAONSnYBdPDoaak6VkCJ/lovYZSoJJBpgB15RuqPq/hrnFAE BhgjAPxAr4+UhygI1IbIAcnf8FD4mG5t35mMVJGPyP7mDH/iHyXdCAG4p1N9TbdB6KhO WbWUTlVPHtIMLSTxc6iXR+qUYTryTVinCEOlIrzMRFh80GT/E5OH/Zsp6h7nFkrg2x0g Jlrd/nXy3gXACnAJ+IsKXbBhULHJXgpl2Srm7ru/5PZZ75i45MNZrWx3VHXXF9uDta0G DfpKDzsvqOVhbsN54W18oopmdkxBmsr4iKPVR+2isgo9+UrwQODcBc8znogrj4R4kbPV PY/w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to:date :cc:to:from:subject:message-id; bh=tVGiAyhaWFFV8P68I0CXKpbEaUMcAV96SdwtrRw3k/w=; b=ZirH6xulMUpeFFzP2LEx908ct+n7wGQ2LEVg1Mprmwl8UGGJJpPrC/ojxXFBaTjNsf g3bwjU7FJF4do7PcCUxVEKdwGfXO8vu/raiD3ieDno+4fzK3yC/nI4U6IiAIbzUpk+kJ t/qruUvyBGorXleFmLU08ZfSW7/LFqaIdQfjZDs3VtvwHbbgC8XPy8dBXFDd5SlOJONY c/0foyyY5mPdaJ53Jtby4rdf62PXNO/5/SSmz0+ur3KCehxnRcRfQxGAgqaifmkBG5Xe vnl3HVQAA/tUgVrO7MEgJ5ONNq/M+fQw6Tfvn4nsebtZeMujnz2KoHrSBenNj3an8aNT 76lw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c10-v6si18072109plr.155.2018.09.18.07.42.00; Tue, 18 Sep 2018 07:42:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729937AbeIRUNW (ORCPT + 99 others); Tue, 18 Sep 2018 16:13:22 -0400 Received: from shelob.surriel.com ([96.67.55.147]:41592 "EHLO shelob.surriel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729197AbeIRUNW (ORCPT ); Tue, 18 Sep 2018 16:13:22 -0400 Received: from imladris.surriel.com ([96.67.55.152]) by shelob.surriel.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1g2HAr-0001f1-Vd; Tue, 18 Sep 2018 10:40:21 -0400 Message-ID: <1e3c2ab11320c1c2f320f9e24ac0d31625bd60e6.camel@surriel.com> Subject: Re: [RFC 00/60] Coscheduling for Linux From: Rik van Riel To: "Jan H." =?ISO-8859-1?Q?Sch=F6nherr?= , Peter Zijlstra Cc: Ingo Molnar , linux-kernel@vger.kernel.org, Paul Turner , Vincent Guittot , Morten Rasmussen , Tim Chen Date: Tue, 18 Sep 2018 10:40:21 -0400 In-Reply-To: <1d86f497-9fef-0b19-50d6-d46ef1c0bffa@amazon.de> References: <20180907214047.26914-1-jschoenh@amazon.de> <20180914111251.GC24106@hirez.programming.kicks-ass.net> <1d86f497-9fef-0b19-50d6-d46ef1c0bffa@amazon.de> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-K5YcfEiG96vCjA3wYFT9" X-Mailer: Evolution 3.28.5 (3.28.5-1.fc28) Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-K5YcfEiG96vCjA3wYFT9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2018-09-14 at 18:25 +0200, Jan H. Sch=C3=B6nherr wrote: > On 09/14/2018 01:12 PM, Peter Zijlstra wrote: > > On Fri, Sep 07, 2018 at 11:39:47PM +0200, Jan H. Sch=C3=B6nherr wrote: > > >=20 > > > B) Why would I want this? > > > In the L1TF context, it prevents other applications from > > > loading > > > additional data into the L1 cache, while one application tries > > > to leak > > > data. > >=20 > > That is the whole and only reason you did this; >=20 > It really isn't. But as your mind seems made up, I'm not going to > bother > to argue. What are the other use cases, and what kind of performance numbers do you have to show examples of workloads where coscheduling provides a performance benefit? --=20 All Rights Reversed. --=-K5YcfEiG96vCjA3wYFT9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEKR73pCCtJ5Xj3yADznnekoTE3oMFAluhDlUACgkQznnekoTE 3oP3cwf7B7g/aayyrfSwUnziwRifp9BU+EM2IVUSW5m0vioYVjkr3zt2D00aAiYQ v8gI9K/9tenserR1I+Gt1f6XHbp/Ht1aaRhmPVqSMk6TJoKHcZNkfihZZwnFoKpf NoKXaEnNVqgSKn5ZD6n6ZQ8c/PYTkBRmu/qoco6KvThNwDbruTKWCuRHfti7ktV4 qqr854sWzQ19C+9qsujQ8C1xoZhGn6I3YKyHG79KUKo8zsrWjvFVuHrmtmJawdww GdPzKnwXlBC3wUW9LAuFwhZIZr4S+gDhZ5i/5xtI40wISZS5vV6gFIQzIhJZh4BO tXnvBDms5QRy2PaSTJ1r/s4yz6b6RQ== =PtBi -----END PGP SIGNATURE----- --=-K5YcfEiG96vCjA3wYFT9--