From: Andrei Kartashev <a.kartashev@yadro.com>
To: Patrick Venture <venture@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Quanta requests to create a repo in OpenBMC github
Date: Fri, 18 Sep 2020 21:22:40 +0300 [thread overview]
Message-ID: <6df4dd0dcc61aa0a11396ec8cfd3d073416ca272.camel@yadro.com> (raw)
In-Reply-To: <CAO=noty_XW8LmRJ3kc7pzjO5n73=70NDhmFk=25zvvJBfmir8Q@mail.gmail.com>
I'm just curious, because I don't really know how does pid-control
actually works. Let's say we have following zone configuration (EM
configuration file, unrelated PID parameters are hidden):
{
"FailSafePercent": 100,
"MinThermalOutput": 30,
"Name": "Main",
"Type": "Pid.Zone"
},
{
"Class": "temp",
"Inputs": [
"DIMM [ABCDEF]\\d+ CPU0",
"DIMM [ABCDEF]\\d+ CPU1"
],
"Name": "DIMM ALL",
"Outputs": [],
"SetPoint": 80.0,
"Type": "Pid",
"Zones": [
"Main"
],
...
},
{
"Class": "temp",
"Inputs": [
"EXIT_AIR"
],
"Name": "EXIT_AIR",
"Outputs": [],
"SetPoint": 50.0,
"Type": "Pid",
"Zones": [
"Main"
],
...
},
{
"Class": "fan",
"Inputs": [
"SYS_FAN"
],
"Name": "SYS_FAN",
"Outputs": [
"SYS_FAN_PWM"
],
"Type": "Pid",
"Zones": [
"Main"
],
...
},
How would it work? I was sure pid-control would examine all the sensors
and try to keep temperature below setpoints: 80 degrees for any of DIMM
memory sensors and 50 degree for exit air. If so, what is the benefit
to use this virtual margin sensor?
On Fri, 2020-09-18 at 08:49 -0700, Patrick Venture wrote:
> On Fri, Sep 18, 2020 at 1:06 AM Andrei Kartashev <
> a.kartashev@yadro.com> wrote:
> >
> > > This daemon is intended to be used in combination with
> > > phosphor-pid-control. You define a configuration file with two
> > > sections: sensors and zones.
> > >
> > > Sensors have a D-Bus path to read from along with a target
> > > temperature
> > > and some other parameters. The daemon subtracks the current
> > > temperature from the target temperature to get the "margin". A
> > > smaller
> > > margin means the temperature is closer to the limit.
> > >
> > > Zones group sensors together and look for the worst (lowest)
> > > margin
> > > value within that group. This value is then exported for use in
> > > phosphor-pid-control.
> >
> > I wonder, isn't phosphor-pid-control do the same by its own? How
> > does
> > it works inside pid-control daemon, when you set several thermal
> > sensors for one Zone an set setpoint for each of them?
>
> Not sure what your question is, but yes, the pid-control daemon can
> host its own margin sensor values that are populated externally,
> however this is only supported via the json configuration at present.
>
> >
> > --
> > Best regards,
> > Andrei Kartashev
> >
> >
--
Best regards,
Andrei Kartashev
next prev parent reply other threads:[~2020-09-18 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 13:30 Quanta requests to create a repo in OpenBMC github Fran Hsu (徐誌謙)
2020-09-16 18:20 ` Benjamin Fair
2020-09-17 5:37 ` Josh Lehan
2020-09-17 15:29 ` Patrick Williams
2020-09-17 23:35 ` Benjamin Fair
2020-09-18 8:05 ` Andrei Kartashev
2020-09-18 15:49 ` Patrick Venture
2020-09-18 18:15 ` Benjamin Fair
2020-09-18 18:22 ` Andrei Kartashev [this message]
2020-09-18 18:28 ` Benjamin Fair
2020-09-25 6:32 ` George Hung (洪忠敬)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6df4dd0dcc61aa0a11396ec8cfd3d073416ca272.camel@yadro.com \
--to=a.kartashev@yadro.com \
--cc=openbmc@lists.ozlabs.org \
--cc=venture@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).