All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "Andi Kleen" <andi@firstfloor.org>,
	"Björn Steinbrink" <B.Steinbrink@gmx.de>,
	"Brown, Len" <len.brown@intel.com>,
	tglx@linutronix.de, mingo@elte.hu, "Zhu, Yi" <yi.zhu@intel.com>,
	linux-kernel@vger.kernel.org, arjan@infradead.org, trenn@suse.de
Subject: Re: Increased ipw2200 power usage with dynticks
Date: Wed, 23 May 2007 14:15:24 +0200	[thread overview]
Message-ID: <20070523121524.GA4999@one.firstfloor.org> (raw)
In-Reply-To: <653FFBB4508B9042B5D43DC9E18836F5EA5415@scsmsx415.amr.corp.intel.com>

> The current idea is that we will have multiple governors changeable at run time only for
> DEBUG and DEVELOPMENT. On a standard end user system there will be one governor
> (current optimal governor) that will be loaded. This gives
> flexibality to experiments with governors and also easily have different governors for
> different kind of platforms - in future if needed (handheld v/s laptop v/s server).
> Also, there are no overheads at runtime due to the fact that we have underlying infrastructure
> to have multiple governors (no locking overheads and such).

For testing/debugging you could just use some ifdefs, right? 

-Andi

  reply	other threads:[~2007-05-23 12:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18 15:46 Increased ipw2200 power usage with dynticks Björn Steinbrink
2007-05-19 17:10 ` Björn Steinbrink
2007-05-20 18:55   ` Andi Kleen
2007-05-21  7:49     ` Björn Steinbrink
2007-05-21 17:24       ` Pallipadi, Venkatesh
2007-05-22  9:23         ` Andi Kleen
2007-05-22 18:00           ` Pallipadi, Venkatesh
2007-05-23 12:15             ` Andi Kleen [this message]
2007-05-22 17:43       ` Bill Davidsen

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=20070523121524.GA4999@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=B.Steinbrink@gmx.de \
    --cc=arjan@infradead.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=trenn@suse.de \
    --cc=venkatesh.pallipadi@intel.com \
    --cc=yi.zhu@intel.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 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.