From: Robert Hancock <hancockr@shaw.ca>
To: Ed Sweetman <safemode2@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86_64 dynticks not working prev: cpuidle, dynticks compatible or no?
Date: Fri, 07 Dec 2007 21:50:36 -0600 [thread overview]
Message-ID: <475A148C.50100@shaw.ca> (raw)
In-Reply-To: <fa.exjBuk8I+Vs1DPTCnfjHA4mJ5iE@ifi.uio.no>
Ed Sweetman wrote:
> System is idle now, previously it was doing something i couldn't halt at
> the time. I'm looking at "Local timer interrupts" in the "Loc:" section
> of /proc/interrupts.
> Across 1 second while the system is pretty much idle, i still get 300
> interrupts. My HZ variable is set to 300 in the kernel config, so this
> is expected but I was under the assumption that dynticks/tickless being
> compiled in would cause that to be much lower.
>
> Am I reading the wrong section of /proc/interrupts to verify if
> dynticks is working or not? Again, i see no difference in cpu temp at all.
Try running powertop ( http://www.lesswatts.org/projects/powertop/ ) and
see what it reports.
I don't think dynticks will generally save huge amounts of power on a
typical desktop machine. The big gains come from being able to stay in
deep sleep C-states (C2/C3) for longer periods of time, but most desktop
machines only enable sleep states down to C1.
>
> In case it helps, this is an athlon64 x2 with apic functioning and both
> cores active in 64bit mode. dmesg is below.
> not related :
> Some additional notes: it87 is my lm_sensor, it doesn't work in this
> kernel, yet it did in 2.6.22. Perhaps enabling high precision timers
> changed something in acpi land.
>
> I enabled tcp dma offloading in this kernel, i get debugging output
> related to it, error is at the last line. No corruption or otherwise
> bad behavior. Transferring via cifs at 9.7MB/sec "incoming" took about
> 15% of one cpu... I never bothered to check if that is the norm but i
> suspect i'll be removing that feature as it seems to not play nice with
> the kernel.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-12-08 3:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.neCPfeOoC5rmM5re+ZzLHNAq2IU@ifi.uio.no>
[not found] ` <fa.exjBuk8I+Vs1DPTCnfjHA4mJ5iE@ifi.uio.no>
2007-12-08 3:50 ` Robert Hancock [this message]
2007-12-08 4:56 ` x86_64 dynticks not working prev: cpuidle, dynticks compatible or no? Ed Sweetman
2007-12-08 5:28 ` Ed Sweetman
2007-12-07 5:38 Ed Sweetman
2007-12-07 22:47 ` x86_64 dynticks not working prev: " Ed Sweetman
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=475A148C.50100@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode2@comcast.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox