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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 17 Feb 2017 14:41:54 +0100 (CET)
From:   Thomas Gleixner <>
To:     Stephane Eranian <>
cc:     "Luck, Tony" <>,
        David Carrillo-Cisneros <>,
        Vikas Shivappa <>,
        "Shivappa, Vikas" <>,
        linux-kernel <>,
        x86 <>, "" <>,
        Ingo Molnar <>,
        Peter Zijlstra <>,
        "Shankar, Ravi V" <>,
        "Yu, Fenghua" <>,
        "Kleen, Andi" <>,
        "Anvin, H Peter" <>
Subject: Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes

On Tue, 7 Feb 2017, Stephane Eranian wrote:
> I think the design must ensure that the following usage models can be monitored:
>    - the allocations in your CAT partitions
>    - the allocations from a task (inclusive of children tasks)
>    - the allocations from a group of tasks (inclusive of children tasks)
>    - the allocations from a CPU
>    - the allocations from a group of CPUs

What's missing here is:

     - the allocations of a subset of users (tasks/groups/cpu(s)) of a
       particular CAT partition

Looking at your requirement list, all requirements, except the first point,
have no relationship to CAT (at least not from your write up). Now the
obvious questions are:

 - Does it make sense to ignore CAT relations in these sets?

 - Does it make sense to monitor a task / group of tasks, where the tasks
   belong to different CAT partitions?

 - Does it make sense to monitor a CPU / group of CPUs as a whole
   independent of which CAT partitions have been utilized during the
   monitoring period?

I don't think it makes any sense, unless the resulting information is split
up into CAT partitions.

I'm happy to be educated on the value of making this CAT unaware, but so
far I only came up with results, which need a crystal ball to analyze them.



Powered by blists - more mailing lists