All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Borg <kentborg@borg.org>
To: Alan Cox <laughing@shared-source.org>
Cc: linux-kernel@vger.kernel.org
Subject: kapm-idled Funny in 2.4.10-ac12?
Date: Fri, 12 Oct 2001 10:12:42 -0400	[thread overview]
Message-ID: <20011012101242.C19336@borg.org> (raw)

Not that it so far appears to be a problem, but where kapm-idled used
to wait a tad after activity and then apparently gobble up all the
extra CPU cycles (in 2.4.10-ac1) I now notice that xosview is showing
CPU usage when things are quiet as hopping up and down, and top is
reporting kapm-idled CPU usage as in the mid to high 50 percent range.

Under 2.4.10-ac1 top used to put kapm-idled in the very high 90
percent range.

Does this mean my laptop will get less battery life?


Thanks,

-kb, the Kent with too wimpy a battery as it is.


P.S.  I am on a Sony Viao PCG-Z505LE.

             reply	other threads:[~2001-10-12 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-12 14:12 Kent Borg [this message]
2001-10-12 14:21 ` kapm-idled Funny in 2.4.10-ac12? Alan Cox
2001-10-12 14:32   ` Peter T. Breuer
2001-10-12 14:35   ` Kent Borg
     [not found] <20011012193019.A612@linux.uib.es>
2001-10-12 18:08 ` Alan Cox

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=20011012101242.C19336@borg.org \
    --to=kentborg@borg.org \
    --cc=laughing@shared-source.org \
    --cc=linux-kernel@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.