From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757201AbcG0RFf (ORCPT ); Wed, 27 Jul 2016 13:05:35 -0400 Received: from mail-it0-f51.google.com ([209.85.214.51]:38330 "EHLO mail-it0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753179AbcG0RFd (ORCPT ); Wed, 27 Jul 2016 13:05:33 -0400 MIME-Version: 1.0 In-Reply-To: <1468371785-53231-16-git-send-email-fenghua.yu@intel.com> References: <1468371785-53231-1-git-send-email-fenghua.yu@intel.com> <1468371785-53231-16-git-send-email-fenghua.yu@intel.com> From: Nilay Vaish Date: Wed, 27 Jul 2016 12:04:51 -0500 Message-ID: Subject: Re: [PATCH 15/32] cacheinfo: Introduce cache id To: Fenghua Yu Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Tony Luck , Tejun Heo , Borislav Petkov , Stephane Eranian , Peter Zijlstra , Marcelo Tosatti , David Carrillo-Cisneros , Ravi V Shankar , Vikas Shivappa , Sai Prakhya , linux-kernel , x86 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12 July 2016 at 20:02, Fenghua Yu wrote: > From: Fenghua Yu > > Each cache is described by cacheinfo and is unique in the same index > across the platform. But there is no id for a cache. We introduce cache > ID to identify a cache. > > Intel Cache Allocation Technology (CAT) allows some control on the > allocation policy within each cache that it controls. We need a unique > cache ID for each cache level to allow the user to specify which > controls are applied to which cache. Cache id is a concise way to specify > a cache. > > Cache id is first enabled on x86. It can be enabled on other platforms > as well. The cache id is not necessary contiguous. > > Add an "id" entry to /sys/devices/system/cpu/cpu*/cache/index*/ Can you explain what index and platform mean? I think those terms are generic in nature. May be an example on how cache ids would be assigned to different caches would help. -- Nilay