All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Patrick Venture <venture@google.com>
Cc: openbmc@lists.ozlabs.org, Nancy Yuen <yuenn@google.com>,
	Matthew Barth <msbarth@linux.vnet.ibm.com>
Subject: Re: phosphor-hwmon bottleneck potential
Date: Fri, 5 May 2017 11:38:02 -0500	[thread overview]
Message-ID: <20170505163802.GD25937@heinlein.lan> (raw)
In-Reply-To: <CAO=notxUh7si0kxbpyA-vK6aJaLQSi5NWCap7SeXDAgUNn8grQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]

On Thu, May 04, 2017 at 09:11:49AM -0700, Patrick Venture wrote:
> Without multi-threading to remove the timing bottleneck on my platform, and
> the inability to provide other more direct interfaces for controlling fans,
> I'll be unable to use phosphor-hwmon as a primary source for
> reading/writing sensor data and will be unable to upstream any effort i
> make to write a pluggable thermal controller.

From what you wrote earlier, it seems like the constraint has nothing to
do with phosphor-hwmon but with the hwmon subsystem for your particular
driver?  How does a "direct interface" avoid the hwmon latency?  I'm 99%
certain that it isn't dbus itself contributing to the 8 second latency
you are seeing here.  Are you arriving at a different conclusion?

-- 
Patrick Williams

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2017-05-05 16:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 16:11 phosphor-hwmon bottleneck potential Patrick Venture
2017-05-05  5:07 ` Brad Bishop
2017-05-05 16:34   ` Patrick Williams
2017-05-05 16:48     ` Rick Altherr
2017-05-05 17:43       ` Patrick Williams
2017-05-05 17:48         ` Rick Altherr
2017-05-05 18:02           ` Patrick Williams
2017-05-05 18:04             ` Patrick Venture
2017-05-05 18:05             ` Rick Altherr
2017-05-05 18:37               ` Nancy Yuen
2017-05-05 18:50                 ` Robi Buranyi
2017-05-05 19:55                   ` Patrick Williams
2017-05-05 18:52                 ` Rick Altherr
2017-05-05 20:13                   ` Patrick Williams
2017-05-05 20:35                 ` Patrick Williams
2017-05-10  1:46                   ` Patrick Venture
2017-05-05 16:38 ` Patrick Williams [this message]

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=20170505163802.GD25937@heinlein.lan \
    --to=patrick@stwcx.xyz \
    --cc=msbarth@linux.vnet.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=venture@google.com \
    --cc=yuenn@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.