public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Bonilla" <abonilla@linuxwireless.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dual Core on Linux questions
Date: Sat, 18 Mar 2006 03:03:40 -0600	[thread overview]
Message-ID: <20060318085954.M66389@linuxwireless.org> (raw)
In-Reply-To: <441BCBAE.2020302@garzik.org>

On Sat, 18 Mar 2006 03:58:22 -0500, Jeff Garzik wrote
> Alejandro Bonilla wrote:
> > Hi,
> > 
> > I have a few questions about the PM Dual Core and how could it really work
> > with Linux. Sorry if there are new patches on LKML about any of these things:
> > 
> > Could each processor or die, have it's own cpufreq scaling governor?
> 
> Sure.  On a laptop, if you don't need dual core power, it makes 
> sense to turn off the unused core, even.
> 
> 	Jeff

Jeff,

For some reason, while I was writing this email, I knew you would be the first
to reply. LOL. Anyway. Does this need new patches sent to LKML or nice
commands to make this work or any idea if stock cpufreqd should manage the
cores separatelly? I haven't got that to work on 2.6.15 so far. How flexible
can we get with the cores?

Thanks for your time,

.Alejandro

  reply	other threads:[~2006-03-18  9:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18  8:35 Dual Core on Linux questions Alejandro Bonilla
2006-03-18  8:58 ` Jeff Garzik
2006-03-18  9:03   ` Alejandro Bonilla [this message]
2006-03-18 10:49     ` Mattia Dongili
2006-03-18  9:21 ` Arjan van de Ven
2006-03-20 19:23 ` Wes Felter
  -- strict thread matches above, loose matches on Subject: below --
2006-03-23  3:36 Pallipadi, Venkatesh
2006-03-23  3:44 ` Jeff Garzik
2006-03-29 19:51   ` Bill Davidsen
2006-03-30 20:31     ` Jeff Garzik
2006-04-04 19:30       ` Bill Davidsen
2006-03-23 17:55 ` Mattia Dongili
2006-03-23  3:51 Pallipadi, Venkatesh

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=20060318085954.M66389@linuxwireless.org \
    --to=abonilla@linuxwireless.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    /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