On Sun, Dec 29, 2019 at 07:43:54PM +0100, Samuel Thibault wrote: > Adam Borowski, le dim. 29 déc. 2019 19:06:08 +0100, a ecrit: > > * URL : https://github.com/kilobyte/topline > > * License : GPL-2+noA > > Programming Lang: C > > Description : per-core/NUMA CPU and disk utilization plain-text > > grapher > > Nice :) > > You would probably want to use the hwloc library to easily get the > topology of the machine (numa nodes, sockets, caches, cores) ;)
Sounds interesting. My tool is simple, and it currently knows about two levels of hierarchy: NUMA nodes and thread siblings. It doesn't care about or show memory cache or tier hierarchy, thus a good part of hwloc data would be irrelevant. It could be nice to show socket->numa nodes hierarchy, however I have yet to access any machine with a non-flat NUMA topology: * servers I know have 2 or 4 sockets, with flat cores->HT on each * fat AMD desktops (like 2990WX I own) have four chiplets in 1 socket * HMEM tiering fake nodes have a hierarchy but NVDIMM nodes have no CPUs * big.LITTLE clusters (like MT6797X 4+4+2) are probably uninteresting Ie, something for the future, but I'm starting small for now. I'll see if there are any users, then see what they want. And there'll be time to extend it, for which your pointer to hwloc will be useful. BTW, I'm not doing this for anything work-related for now, but mostly because of an idea I came with while messing with zdebootstrap (which I haven't have tuits to mess with since June :( ). Meow! -- ⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, ⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month. ⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake, ⠈⠳⣄⠀⠀⠀⠀ etc), let the drink age at least 3-6 months.
