[–] mrflop 3mo ago ↗ Renaming fopen64 to intercept library calls feels like a brittle hack masquerading as "sandboxing." Why not just upstream this hardware support to nvtop instead of fragmenting the ecosystem? [–] marwanet 3mo ago ↗ If this logic were pushed into nvtop, wouldn't the codebase become unmaintainable? Each vendor's interception method is going to be different.
[–] marwanet 3mo ago ↗ If this logic were pushed into nvtop, wouldn't the codebase become unmaintainable? Each vendor's interception method is going to be different.
[–] rdyro 3mo ago ↗ Looks cool!nvtop can actually support TPUs too via https://github.com/rdyro/libtpuinfo/ https://github.com/Syllo/nvtop/blob/76890233d759199f50ad3bdb...
[–] serialx 3mo ago ↗ Look into all-smi https://github.com/lablup/all-smi It supports all GPUs thinkable including Apple Silicon and many AI accelerator cards.
[–] synergy20 3mo ago ↗ would be nice to have cpu usage added so I have all in one?currently I use btop which shows basic gpu load along with cpu, network, etc.
7 comments
[ 3.0 ms ] story [ 30.3 ms ] threadnvtop can actually support TPUs too via https://github.com/rdyro/libtpuinfo/ https://github.com/Syllo/nvtop/blob/76890233d759199f50ad3bdb...
currently I use btop which shows basic gpu load along with cpu, network, etc.