zeldon
/
htop
mirror of https://github.com/xzeldon/htop.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
htop/freebsd/Platform.h

52 lines
1.1 KiB
C
Raw Normal View History

Beginnings of FreeBSD port!
2014-11-27 18:27:34 +00:00
/* Do not edit this file. It was automatically generated. */
#ifndef HEADER_Platform
#define HEADER_Platform
/*
Uptime meter for FreeBSD. This will produce too much replicated code. I think I'll use a lighter abstraction in things like this.
2014-11-27 21:33:37 +00:00
htop - freebsd/Platform.h
Beginnings of FreeBSD port!
2014-11-27 18:27:34 +00:00
(C) 2014 Hisham H. Muhammad
Released under the GNU GPL, see the COPYING file
in the source distribution for its full text.
*/
#include "Action.h"
Add a stub for the battery meter.
2014-11-27 23:07:42 +00:00
#include "BatteryMeter.h"
Regenerate platform-dependent headers. Closes #293.
2015-10-19 19:22:54 +00:00
#include "SignalsPanel.h"
Beginnings of FreeBSD port!
2014-11-27 18:27:34 +00:00
Get FreeBSD tree to compile again with latest changes.
2015-03-16 06:13:42 +00:00
extern ProcessFieldData Process_fields[];
Introduce CLAMP macro. Unify all MIN(MAX(a,b),c) uses. With the CLAMP macro replacing the combination of MIN and MAX, we will have at least two advantages: 1. It's more obvious semantically. 2. There are no more mixes of confusing uses like MIN(MAX(a,b),c) and MAX(MIN(a,b),c) and MIN(a,MAX(b,c)) appearing everywhere. We unify the 'clamping' with a single macro. Note that the behavior of this CLAMP macro is different from the combination `MAX(low,MIN(x,high))`. * This CLAMP macro expands to two comparisons instead of three from MAX and MIN combination. In theory, this makes the code slightly smaller, in case that (low) or (high) or both are computed at runtime, so that compilers cannot optimize them. (The third comparison will matter if (low)>(high); see below.) * CLAMP has a side effect, that if (low)>(high) it will produce weird results. Unlike MIN & MAX which will force either (low) or (high) to win. No assertion of ((low)<=(high)) is done in this macro, for now. This CLAMP macro is implemented like described in glib <http://developer.gnome.org/glib/stable/glib-Standard-Macros.html> and does not handle weird uses like CLAMP(a++, low++, high--) .
2016-01-15 12:26:01 +00:00
#ifndef CLAMP
#define CLAMP(x,low,high) (((x)>(high))?(high):(((x)<(low))?(low):(x)))
#endif
Get FreeBSD tree to compile again with latest changes.
2015-03-16 06:13:42 +00:00
extern ProcessField Platform_defaultFields[];
extern int Platform_numberOfFields;
Mark signal tables 'const' Specifically, Platform_signals[] and Platform_numberOfSignals. Both are not supposed to be mutable. Marking them 'const' puts them into rodata sections in binary. And for Platform_numberOfSignals, this aids optimization (aids only Link Time Optimization for now). :) Signed-off-by: Kang-Che Sung <explorer09@gmail.com>
2016-08-30 12:41:17 +00:00
extern const SignalItem Platform_signals[];
Regenerate platform-dependent headers. Closes #293.
2015-10-19 19:22:54 +00:00
Mark signal tables 'const' Specifically, Platform_signals[] and Platform_numberOfSignals. Both are not supposed to be mutable. Marking them 'const' puts them into rodata sections in binary. And for Platform_numberOfSignals, this aids optimization (aids only Link Time Optimization for now). :) Signed-off-by: Kang-Che Sung <explorer09@gmail.com>
2016-08-30 12:41:17 +00:00
extern const unsigned int Platform_numberOfSignals;
Regenerate platform-dependent headers. Closes #293.
2015-10-19 19:22:54 +00:00
Beginnings of FreeBSD port!
2014-11-27 18:27:34 +00:00
void Platform_setBindings(Htop_Action* keys);
Uptime meter for FreeBSD. This will produce too much replicated code. I think I'll use a lighter abstraction in things like this.
2014-11-27 21:33:37 +00:00
extern MeterClass* Platform_meterTypes[];
Add uptime calculation code.
2014-11-27 21:44:20 +00:00
int Platform_getUptime();
Beginnings of FreeBSD port!
2014-11-27 18:27:34 +00:00
Load averages for FreeBSD!
2014-11-27 22:03:29 +00:00
void Platform_getLoadAverage(double* one, double* five, double* fifteen);
"get max pid" for FreeBSD
2014-11-27 22:18:01 +00:00
int Platform_getMaxPid();
Get FreeBSD tree to compile again with latest changes.
2015-03-16 06:13:42 +00:00
double Platform_setCPUValues(Meter* this, int cpu);
void Platform_setMemoryValues(Meter* this);
void Platform_setSwapValues(Meter* this);
Add a stub for the battery meter.
2014-11-27 23:07:42 +00:00
Get FreeBSD tree to compile again with latest changes.
2015-03-16 06:13:42 +00:00
void Platform_setTasksValues(Meter* this);
Add a stub for the battery meter.
2014-11-27 23:07:42 +00:00
Introduce CLAMP macro. Unify all MIN(MAX(a,b),c) uses. With the CLAMP macro replacing the combination of MIN and MAX, we will have at least two advantages: 1. It's more obvious semantically. 2. There are no more mixes of confusing uses like MIN(MAX(a,b),c) and MAX(MIN(a,b),c) and MIN(a,MAX(b,c)) appearing everywhere. We unify the 'clamping' with a single macro. Note that the behavior of this CLAMP macro is different from the combination `MAX(low,MIN(x,high))`. * This CLAMP macro expands to two comparisons instead of three from MAX and MIN combination. In theory, this makes the code slightly smaller, in case that (low) or (high) or both are computed at runtime, so that compilers cannot optimize them. (The third comparison will matter if (low)>(high); see below.) * CLAMP has a side effect, that if (low)>(high) it will produce weird results. Unlike MIN & MAX which will force either (low) or (high) to win. No assertion of ((low)<=(high)) is done in this macro, for now. This CLAMP macro is implemented like described in glib <http://developer.gnome.org/glib/stable/glib-Standard-Macros.html> and does not handle weird uses like CLAMP(a++, low++, high--) .
2016-01-15 12:26:01 +00:00
char* Platform_getProcessEnv(pid_t pid);
Beginnings of FreeBSD port!
2014-11-27 18:27:34 +00:00
#endif