On Tue, Jun 27, 2017 at 03:48:55PM +0000, Duran, Leo wrote: > Basically, in our case a Package may contain more than one L3 (i.e., > in hardware terms, there may more than one 'Core complex' in a 'Die'). > The important point is that all logical processors (threads) that > share an L3 have a common "cpu_llc_id".
All that means nothing if it doesn't have any effect on scheduling. If moving the working set between L3s within the package, as you call it, is not measureable, i.e., task migration, then we don't care. The whole exercise is not about modelling the hardware topology accurately but for presenting sufficient detailed topology to the scheduler so that it works optimally on Zen. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.