a) the information in /proc/stat is actually much denser since it's
"cpu VAL VAL VAL VAL" as opposed to "cpuX.FIELD VAL"
b) If it became a problem the /proc/stat case is actually fairlyThat can be done.
trivially fixable by defining each cpu as a record and "everything
else" as a magic im-out-of-cpus value.
>As I prefaced, I'm not sure there's much that can be trivially done
> Now, if you guys are okay with a file per-cpu, I can do it as well.
> It pollutes the filesystem, but at least protects against the fact that this
> is kmalloc-backed.
>
about it. This is really a fundamental limitation of how read_map()
works.
What we really need is a proper seq_file exposed through cftypes.