htop/darwin/DarwinProcessList.h

38 lines
919 B
C
Raw Normal View History

#ifndef HEADER_DarwinProcessList
#define HEADER_DarwinProcessList
/*
htop - DarwinProcessList.h
(C) 2014 Hisham H. Muhammad
Released under the GNU GPLv2, see the COPYING file
in the source distribution for its full text.
*/
#include <mach/mach_host.h>
#include <sys/sysctl.h>
2019-07-07 21:30:37 +00:00
2015-07-14 02:02:40 +00:00
#include "ProcessList.h"
#include "zfs/ZfsArcStats.h"
2015-07-13 06:17:14 +00:00
typedef struct DarwinProcessList_ {
ProcessList super;
2015-07-13 21:53:46 +00:00
host_basic_info_data_t host_info;
vm_statistics_data_t vm_stats;
2015-07-13 22:09:18 +00:00
processor_cpu_load_info_t prev_load;
processor_cpu_load_info_t curr_load;
2015-07-14 02:02:40 +00:00
uint64_t kernel_threads;
uint64_t user_threads;
2015-07-14 16:46:16 +00:00
uint64_t global_diff;
2019-07-07 21:30:37 +00:00
ZfsArcStats zfs;
2015-07-13 06:17:14 +00:00
} DarwinProcessList;
Add a new DynamicMeter class for runtime Meter extension This commit is based on exploratory work by Sohaib Mohamed. The end goal is two-fold - to support addition of Meters we build via configuration files for both the PCP platform and for scripts ( https://github.com/htop-dev/htop/issues/526 ) Here, we focus on generic code and the PCP support. A new class DynamicMeter is introduced - it uses the special case 'param' field handling that previously was used only by the CPUMeter, such that every runtime-configured Meter is given a unique identifier. Unlike with the CPUMeter this is used internally only. When reading/writing to htoprc instead of CPU(N) - where N is an integer param (CPU number) - we use the string name for each meter. For example, if we have a configuration for a DynamicMeter for some Redis metrics, we might read and write "Dynamic(redis)". This identifier is subsequently matched (back) up to the configuration file so we're able to re-create arbitrary user configurations. The PCP platform configuration file format is fairly simple. We expand configs from several directories, including the users homedir alongside htoprc (below htop/meters/) and also /etc/pcp/htop/meters. The format will be described via a new pcp-htop(5) man page, but its basically ini-style and each Meter has one or more metric expressions associated, as well as specifications for labels, color and so on via a dot separated notation for individual metrics within the Meter. A few initial sample configuration files are provided below ./pcp/meters that give the general idea. The PCP "derived" metric specification - see pmRegisterDerived(3) - is used as the syntax for specifying metrics in PCP DynamicMeters.
2021-06-23 07:44:56 +00:00
ProcessList* ProcessList_new(UsersTable* usersTable, Hashtable* dynamicMeters, Hashtable* pidMatchList, uid_t userId);
void ProcessList_delete(ProcessList* this);
void ProcessList_goThroughEntries(ProcessList* super, bool pauseProcessUpdate);
#endif