Nathan Scott

There are already operating-system specific categories in MemoryMeter (compressed). And FWLIW, "buffers" doesn't mean anything sensible anymore for at least two modern Linux filesystems (btrfs and xfs). There's no reason...

> The main reason is that it would be hellish to document them in the man page, where there would be no OS-specific descriptions. There is no documentation of the...

| FreeBSD uses a unified cache and both categories are not separable. This is often true on Linux also - xfs and btrfs use a unified page cache approach. TBH,...

| htop's memory display cannot be 1:1 matching FreeBSD top's display. Sure it can. I'm not saying it has to, though (looks like good progress toward the first option I...

Has any performance comparison been done that is sufficiently compelling that we'd want to keep all this extra code, instead of just using qsort? Thanks.

Sort stability is about what happens when two items compare equally (which can happen with/without multiple sort keys, so I don't follow your argument there). In htop, we always have...

I have read those, yes - there's little/no justification there for custom sort implementations. It seemed like there was consensus that qsort would be fine based on Hishams reasons for...

@Explorer09 I did a little more digging and have found all supported htop platforms have a variant of qsort_r - IIRC you mentioned earlier that its missing somewhere? (even modern...

| The catch is how to detect the calling conventions. Each platform will know the conventions of its own qsort_r, and a xxx/Platform.h wrapper can map that to whichever convention...

> I do observe that something is amiss in the (system wide) /proc/pressure/cpu file. This is expected - its a backwards-compatibility line, the kernel no longer updates 'full' CPU PSI...