From: Bill Davidsen <davidsen@tmr.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Mattia Dongili <malattia@linux.it>,
Alejandro Bonilla <abonilla@linuxwireless.org>,
linux-kernel@vger.kernel.org
Subject: Re: Dual Core on Linux questions
Date: Tue, 04 Apr 2006 15:30:59 -0400 [thread overview]
Message-ID: <4432C973.9080509@tmr.com> (raw)
In-Reply-To: <442C4034.1060203@garzik.org>
Jeff Garzik wrote:
> Bill Davidsen wrote:
>> Jeff Garzik wrote:
>>> Pallipadi, Venkatesh wrote:
>>>>> From cpufreq perspective multiple things are possible in the way
>>>> processor will support the multi-core frequency changing. and most of
>>>> the things are handled at cpufreq inside kernel. I think there
>>>> should be
>>>> minima changes required in cpufreqd if any.
>>>> Options:
>>>
>>>
>>> 4) we power down a core.
>>>
>> Is this just for completeness of the set, something someone might do
>> someday, or does someone really have a hotplug core product?
>
> Not hotplug, just power it down.
>
Is that actually possible on any current hardware? I didn't see it in
any doc I have, but it's all "CPU specs for dummies." ;-)
next prev parent reply other threads:[~2006-04-05 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 3:36 Dual Core on Linux questions 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 [this message]
2006-03-23 17:55 ` Mattia Dongili
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 3:51 Pallipadi, Venkatesh
2006-03-18 8:35 Alejandro Bonilla
2006-03-18 8:58 ` Jeff Garzik
2006-03-18 9:03 ` Alejandro Bonilla
2006-03-18 10:49 ` Mattia Dongili
2006-03-18 9:21 ` Arjan van de Ven
2006-03-20 19:23 ` Wes Felter
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=4432C973.9080509@tmr.com \
--to=davidsen@tmr.com \
--cc=abonilla@linuxwireless.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malattia@linux.it \
/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