From: Con Kolivas <kernel@kolivas.org>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
Daniel Petrini <d.pensator@gmail.com>,
Tony Lindgren <tony@atomide.com>,
vatsa@in.ibm.com, ck list <ck@vds.kolivas.org>,
Pavel Machek <pavel@ucw.cz>, Adam Belay <abelay@novell.com>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>
Subject: Re: [PATCH] i386 No Idle HZ aka dynticks 051217
Date: Mon, 19 Dec 2005 02:22:37 +1100 [thread overview]
Message-ID: <200512190222.40399.kernel@kolivas.org> (raw)
In-Reply-To: <200512190219.40631.kernel@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
On Monday 19 December 2005 02:19, Con Kolivas wrote:
> Here is yet another updated version of the dynticks code.
>
> Changes:
>
> Numerous cleanups, microoptimisations and locking improvements.
>
> One bugfix for the next tick accounting used in early_dyn_reprogram
>
> I've yet to find the cause for grossly high cpu accounting on SMP. I'd
> appreciate any help in this area as it's the last showstopper for this
> code.
>
> Obvious power savings are evident on uniprocessor now in on/off comparisons
> using pmstats.
That would be dynticks-051218 I mean, sorry.
Cheers,
Con
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-18 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 15:19 [PATCH] i386 No Idle HZ aka dynticks 051217 Con Kolivas
2005-12-18 15:22 ` Con Kolivas [this message]
2005-12-18 22:34 ` Con Kolivas
2005-12-19 0:10 ` ACPI C-States [Was: Re: [PATCH] i386 No Idle HZ aka dynticks 051217] Dominik Brodowski
2005-12-19 0:10 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2005-12-17 5:22 [PATCH] i386 No Idle HZ aka dynticks 051217 Con Kolivas
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=200512190222.40399.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=abelay@novell.com \
--cc=ck@vds.kolivas.org \
--cc=d.pensator@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=pavel@ucw.cz \
--cc=tony@atomide.com \
--cc=vatsa@in.ibm.com \
--cc=zwane@arm.linux.org.uk \
/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.