Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933906AbbKSNo0 (ORCPT ); Thu, 19 Nov 2015 08:44:26 -0500 Received: from mx1.redhat.com ([209.132.183.28]:51911 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757743AbbKSNoY (ORCPT ); Thu, 19 Nov 2015 08:44:24 -0500 Date: Thu, 19 Nov 2015 08:44:22 -0500 From: Luiz Capitulino To: Thomas Gleixner Cc: Marcelo Tosatti , LKML , Peter Zijlstra , x86@kernel.org, Vikas Shivappa , Tejun Heo , Yu Fenghua Subject: Re: [RFD] CAT user space interface revisited Message-ID: <20151119084422.5f80250c@redhat.com> In-Reply-To: References: <20151118223405.GA25754@amt.cnet> <20151119003414.GA28388@amt.cnet> Organization: Red Hat MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 793 Lines: 18 On Thu, 19 Nov 2015 09:35:34 +0100 (CET) Thomas Gleixner wrote: > > Well any work on behalf of the important task, should have its cache > > protected as well (example irq handling threads). > > Right, but that's nothing you can do automatically and certainly not > from a random application. Right and that's not a problem. For the use-cases CAT is intended to, manual and per-workload system setup is very common. Things like thread pinning, hugepages reservation, CPU isolation, nohz_full, etc require manual setup too. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/