Hi Daniel,
I agree that to expose othe level cache but the only can be tuned (allocation). If we expose such kinds of information, the host should have ability to control such kinds of resources.
In another thread, Martin told that there are cases which multiple sockets may has different values, I kinds of agree(but I don’t see that case), I agree to expose cache per socket, just wonder if
cell == socket in libvirt? In my environment, I can see all socket_id in a cell are the same, wonder if I can extend cache information to cell node?
Best Regards
Eli Qiao(乔立勇）OpenStack Core team OTC Intel.
--
On 11/01/2017, 9:31 AM, "Qiao, Liyong" <liyong.qiao@xxxxxxxxx> wrote:
> Also, why only l3 cache. Why not expose full info about
> the CPU cache hierarchy. It feels wrong to expose only
> L3 cache and ignore other levels of cache.
Okay, I’ll think how to expose there into capabilities. This is related to enable cache tune support in [1]
The status in kernel is that only L3 cache can be tuned(by cat_l3 support in kernel) for now.
Could you help to give some input for the RFC of cache tune?
[1]https://www.redhat.com/archives/libvir-list/2017-January/msg00354.html
Thanks Eli.
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list
