environment: include memory stats in the results

[Arno500]

This is useful for our performance score calculator and is generally a good metric to dump I think

[ErwanAliasr1]

If you aim at dumping memory information in a matter of computing performance metric, the memory architecture of the machine should be collected.

Adding the memory module dump in the existing dmi code is probably the way to go, adding the memory hierarchy (with hwloc) is also probably a good idea.

I really don't understand how you want to correlate proc/meminfo with performance.

[Arno500]

If you aim at dumping memory information in a matter of computing performance metric, the memory architecture of the machine should be collected.

Adding the memory module dump in the existing dmi code is probably the way to go, adding the memory hierarchy (with hwloc) is also probably a good idea.

I really don't understand how you want to correlate proc/meminfo with performance.

It's more about getting an "amount" than actual performance. The performance metrics related to memory shall be tested in benchmarks and the architectural difference should be included in the benchmark results.

About DMI, I thought about it but:

• it does not work in all environments (for instance, does not work in WSL/Hyper-V it seems, what about other hypervisors?)
• it does not include all forms of actual usable memory (like CXL or swap? No idea of what kind of memory will exist in the future)
• it may possibly be badly integrated by OEMs, or be plain wrong

I still think it could be a good idea FAR, that said

[anisse]

LGTM

DMI can be added in another review, included memstat in "software" environment