All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: abelay@novell.com, len.brown@intel.com,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux@dominikbrodowski.net, arjan@linux.intel.com
Subject: Re: [RFC][PATCH 2/2] ACPI: handle timer ticks proactively
Date: Tue, 5 Sep 2006 11:03:28 +0200	[thread overview]
Message-ID: <20060905090328.GA4888@elf.ucw.cz> (raw)
In-Reply-To: <20060905085319.GA2237@elf.ucw.cz>

Hi!

> > > This patch takes advantage of the infrastructure introduced in the last
> > > patch, and allows the processor idle algorithm to proactively choose a
> > > c-state based on the time the next timer interrupt is expected to occur.
> > > It preserves the residency metric, so the algorithm should, in theory,
> > > remain effective against bursts of activity from other interrupt
> > > sources.
> > > 
> > > This patch is mostly intended to be illustrative.  There may be some
> > > "#ifdef CONFIG_ACPI" issues, and I would appreciate any advice on
> > > implementing this more cleanly.
> 
> Okay, just to get you some feedback:
> 
> It seems to change things a _lot_. Power consumption with usb modules
> loaded went from 14315mW to 13800mW -- that is huge
> deal. Unfortunately something strange is going on: with stock kernel,
> power consumption is mostly constant. With your patch, it varies a
> lot, at 2 second timescale.
> 
> Power consumption with usb unloaded (only way to get reasonable power
> on x60) went from stable 10450mW to  something rapidly changing, and
> probably even worse than original:

I also noticed that with your patch, bus master activity tends to be constant?!

root@amd:/data/l/tp/tp_smapi-0.22# cat /proc/acpi/processor/CPU0/power
active state:            C3
max_cstate:              C8
bus master activity:     37244
states:
    C1:                  type[C1] latency[000] usage[00000067]
duration[00000000000000000067]
    C2:                  type[C2] latency[001] usage[00042173]
duration[00000000000454647687]
   *C3:                  type[C3] latency[057] usage[00290242]
duration[00000000003402855375]
root@amd:/data/l/tp/tp_smapi-0.22# cat /proc/acpi/processor/CPU0/power
active state:            C3
max_cstate:              C8
bus master activity:     37244
states:
    C1:                  type[C1] latency[000] usage[00000067]
duration[00000000000000000067]
    C2:                  type[C2] latency[001] usage[00042274]
duration[00000000000454688808]
   *C3:                  type[C3] latency[057] usage[00305466]
duration[00000000003595077816]
root@amd:/data/l/tp/tp_smapi-0.22#
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-09-05 10:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060904131027.GD6279@ucw.cz>
2006-09-05  8:28 ` [RFC][PATCH 2/2] ACPI: handle timer ticks proactively Pavel Machek
2006-09-05  8:53   ` Pavel Machek
2006-09-05  9:03     ` Pavel Machek [this message]
2006-09-05 15:16       ` Adam Belay
2006-09-06 10:54         ` Pavel Machek
2006-08-29 20:51 Adam Belay
2006-10-16  4:59 ` Len Brown

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=20060905090328.GA4888@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=abelay@novell.com \
    --cc=arjan@linux.intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    /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.