All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] dme1737 very slow read...
Date: Thu, 26 Jul 2007 05:14:20 +0000	[thread overview]
Message-ID: <46A82DAC.5070609@sandeen.net> (raw)
In-Reply-To: <46A8157E.7040003@sandeen.net>

Juerg Haefliger wrote:
> Hi Eric,
> 
> 
>> I was very happy to see dme1737 support added, thank you!  Now I can get
>> all the info out of my compaq sr1710nx cheapo server.  :)
> 
> Glad you like it :-) I can finally tell my wife that the time I spent
> on the driver wasn't all wasted...

I'm impressed; I tried to dislodge a data sheet for this chip from SMSC,
with no luck.  They don't want us to know our cpu temps it seems!  ;-)

>> 1.53 seconds to read "0\n" !  :)
>>
>> Any idea if this is a hardware or software delay?  I haven't yet dug
>> into profiling the kernel code to see what might be taking so long...
> 
> It's simple: We have to read a lot of registers which we can only get
> to via I2C which is veeerrrrryyyyy sloooooowwwwww.

Ok, I thought it might be along those lines.  Is there any other
performance impact to the system while it's waiting for the I2C bus?

Thanks,

-Eric

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2007-07-26  5:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26  3:31 [lm-sensors] dme1737 very slow read Eric Sandeen
2007-07-26  3:58 ` Juerg Haefliger
2007-07-26  5:14 ` Eric Sandeen [this message]
2007-07-26  5:39 ` Juerg Haefliger
2007-07-26  5:42 ` Juerg Haefliger
2007-07-26 11:39 ` Mark M. Hoffman
2007-08-12 12:15 ` Jean Delvare
2007-08-12 14:43 ` Mark M. Hoffman

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=46A82DAC.5070609@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=lm-sensors@vger.kernel.org \
    /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.