Age | Commit message (Collapse) | Author |
|
|
|
Following up with some discusson from a few months back,
where it was proposed that ProcessTable is a better name.
This data structure is definitely not a list ... if it
was one-dimensional it'd be a set, but in practice it has
much more in common with a two-dimensional table.
The Process table is a familiar operating system concept
for many people too so it resonates a little in that way
as well.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
implementation
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Related to https://github.com/hishamhm/htop/issues/992
|
|
|
|
|
|
|
|
|
|
Fixes #738.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
See https://bugzilla.redhat.com/show_bug.cgi?id=987805 for details.
(thanks to Dawid Gajownik for the detailed analysis!)
|
|
|
|
(thanks to Patrick Marlier)
|
|
selected fields.
On my machine, this gives a ~20% improvement in htop process time use with the default config.
|
|
(thanks to Jann Horn)
|
|
(thanks to Rob Hoelz)
|