All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] TODO: "dynamic" sysfs callbacks
Date: Sun, 03 Sep 2006 06:41:35 +0000	[thread overview]
Message-ID: <20060903064135.GA11525@kroah.com> (raw)
In-Reply-To: <44F1E5B6.1080105@gmail.com>

On Sun, Sep 03, 2006 at 08:08:02AM +0200, Jean Delvare wrote:
> Greg KH wrote:
> > On Sat, Sep 02, 2006 at 10:57:03PM +0200, Jean Delvare wrote:
> > > The bus driver msleep()s, so it's rather an uninterruptible sleep?
> > 
> > Yes it is.
> > 
> > > Not that I know what different it makes in that context.
> > 
> > When you sleep in the kernel, in an uninterruptable state, it increases
> > the load average spit out by the kernel by 1.  Now this really doesn't
> > make that much sense, as the code is sleeping and not doing anything at
> > all, but it plays havoc on tools that look at the load average of the
> > machine to see what is going on.
> > 
> > That might be why users think the driver is taking up more cpu time than
> > it really is, but it all depends on how they were measuring it.
> 
> OK, Thanks for the explanation. Isn't it possible to change the kernel
> to not count sleeping processes in the load? That'd make people happier,
> and the value more meaningful.

From what I remember, no, it is not simple to do this.  But feel free to
poke at it, I really don't know how that code works :)

good luck,

greg k-h


      parent reply	other threads:[~2006-09-03  6:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-27 18:34 [lm-sensors] TODO: "dynamic" sysfs callbacks Jim Cromie
2006-09-01 12:33 ` Jean Delvare
2006-09-01 22:08 ` Greg KH
2006-09-02  6:52 ` Jean Delvare
2006-09-02  7:08 ` Greg KH
2006-09-02 14:24 ` Jean Delvare
2006-09-02 18:27 ` Greg KH
2006-09-02 20:57 ` Jean Delvare
2006-09-03  1:46 ` Greg KH
2006-09-03  6:08 ` Jean Delvare
2006-09-03  6:41 ` Greg KH [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=20060903064135.GA11525@kroah.com \
    --to=greg@kroah.com \
    --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.