public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org, tuukka.tikkanen@elektrobit.com,
	ck@vds.kolivas.org
Subject: Re: [patch] i386 dynamic ticks 2.6.13-rc4 (code reordered)
Date: Tue, 2 Aug 2005 00:21:33 -0700	[thread overview]
Message-ID: <20050802072132.GH15903@atomide.com> (raw)
In-Reply-To: <200508021443.55429.kernel@kolivas.org>

* Con Kolivas <kernel@kolivas.org> [050801 21:41]:
> This is a code reordered version of the dynamic ticks patch from Tony Lindgen 
> and Tuukka Tikkanen - sorry about spamming your mail boxes with this, but 
> thanks for the code. There is significant renewed interest by the lkml 
> audience for such a feature which is why I'm butchering your code (sorry 
> again if you don't like me doing this). The only real difference between your 
> code and this patch is moving the #ifdef'd code out of code paths and putting 
> it into dyn-tick specific files. 

Great! We ported it from ARM to x86 so people could develop it further. Help
is really appreciated to get it into shape for integration.

> This has slightly more build fixes than the last one I posted and boots and 
> runs fine on my laptop. So far at absolute idle it appears this pentiumM 1.7 
> is claiming to have _25%_ more battery life. I'll need to investigate further 
> to see the real power savings. 

What is your HZ according to pmstats?

> My desktop pentium4 did not like the patch erroring with "bad gzip magic 
> number" on boot for reasons that aren't obvious to me. This could be related 
> to trying gcc 4.0.1 on that box whereas the laptop is on gcc 3.4.4 and is 
> working fine.

Yeah, this sounds like an issue with the decompression code.

Tony

  parent reply	other threads:[~2005-08-02  7:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02  4:43 [patch] i386 dynamic ticks 2.6.13-rc4 (code reordered) Con Kolivas
2005-08-02  5:35 ` [ck] " Michael Marineau
2005-08-02  5:49 ` Con Kolivas
2005-08-02  5:52   ` Lee Revell
2005-08-02  5:56     ` Con Kolivas
2005-08-02  6:24       ` Lee Revell
2005-08-02  7:17         ` Tony Lindgren
2005-08-02  7:39           ` Con Kolivas
2005-08-02  8:15             ` Tony Lindgren
2005-08-02 10:54               ` Con Kolivas
2005-08-02 11:31                 ` Tony Lindgren
2005-08-02 12:04                   ` Con Kolivas
2005-08-02  7:21 ` Tony Lindgren [this message]
2005-08-02 14:01 ` Avuton Olrich
2005-08-02 14:05   ` Con Kolivas
2005-08-06 14:54 ` Theodore Ts'o
2005-08-06 15:00   ` Con Kolivas
2005-08-08  5:43     ` Stefan Seyfried
2005-08-08 21:54     ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2005-08-08 18:37 Pallipadi, Venkatesh
2005-08-10  6:44 ` Thomas Renninger
2005-08-10  6:57   ` 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=20050802072132.GH15903@atomide.com \
    --to=tony@atomide.com \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tuukka.tikkanen@elektrobit.com \
    /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