Searched hist:ce6a3f36cedc2f822fb446bc5094eaeab47eb4af (Results 1 – 3 of 3) sorted by relevance
/openbmc/phosphor-pid-control/pid/ |
H A D | pidloop.hpp | ce6a3f36cedc2f822fb446bc5094eaeab47eb4af Tue Mar 12 13:20:16 CDT 2019 James Feist <james.feist@linux.intel.com> Remove threads
This converts phosphor-pid-control into an async single threaded application. The reason for doing this is on our systems phosphor-pid-control had the largest VSZ when viewed under top. Before this patch the VSZ was at 50720, after it is at 7760.
Tested-by: Could still interact with all interfaces under rest-dbus and sensor override worked to ramp fans when changing cpu temps.
Change-Id: Ie0a837bdf0d1b1df61dc7aff87e5d503b9e0e875 Signed-off-by: James Feist <james.feist@linux.intel.com>
|
H A D | pidloop.cpp | ce6a3f36cedc2f822fb446bc5094eaeab47eb4af Tue Mar 12 13:20:16 CDT 2019 James Feist <james.feist@linux.intel.com> Remove threads
This converts phosphor-pid-control into an async single threaded application. The reason for doing this is on our systems phosphor-pid-control had the largest VSZ when viewed under top. Before this patch the VSZ was at 50720, after it is at 7760.
Tested-by: Could still interact with all interfaces under rest-dbus and sensor override worked to ramp fans when changing cpu temps.
Change-Id: Ie0a837bdf0d1b1df61dc7aff87e5d503b9e0e875 Signed-off-by: James Feist <james.feist@linux.intel.com>
|
/openbmc/phosphor-pid-control/ |
H A D | main.cpp | diff ce6a3f36cedc2f822fb446bc5094eaeab47eb4af Tue Mar 12 13:20:16 CDT 2019 James Feist <james.feist@linux.intel.com> Remove threads
This converts phosphor-pid-control into an async single threaded application. The reason for doing this is on our systems phosphor-pid-control had the largest VSZ when viewed under top. Before this patch the VSZ was at 50720, after it is at 7760.
Tested-by: Could still interact with all interfaces under rest-dbus and sensor override worked to ramp fans when changing cpu temps.
Change-Id: Ie0a837bdf0d1b1df61dc7aff87e5d503b9e0e875 Signed-off-by: James Feist <james.feist@linux.intel.com>
|