cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: davej@redhat.com, cpufreq@www.linux.org.uk
Subject: Re: [PATCH] cpufreq: 1/4 SMT awareness: save cpumask_t cpus
Date: Mon, 30 Aug 2004 22:04:38 +0200	[thread overview]
Message-ID: <20040830200438.GC8563@dominikbrodowski.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0408301229020.21527@montezuma.fsmlabs.com>

On Mon, Aug 30, 2004 at 12:45:19PM -0400, Zwane Mwaikambo wrote:
> On Sun, 29 Aug 2004, Dominik Brodowski wrote:
> 
> > Actually, I do favor "2" by large, and there simply may not be "dumb"
> > governors once we propagate the SMT awareness to the cpufreq core. Zwane,
> > are you aware of my current patch set which aims at the same direction? IIRC
> > [and my memory might be a bit off after a long vacation], it mostly needs
> > work from the "governor" perspective -- and testing. Don't have hardware
> > here...
> 
> Yeah, i saw the patches and indeed the work should be done in the
> governor, i should be able to help with the testing.

Excellent. Will try to update my patches soon.

Thanks,
	Dominik

  reply	other threads:[~2004-08-30 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 16:46 [PATCH] cpufreq: 1/4 SMT awareness: save cpumask_t cpus Pallipadi, Venkatesh
2004-08-20  5:35 ` Zwane Mwaikambo
2004-08-29 13:01   ` Dominik Brodowski
2004-08-30 16:45     ` Zwane Mwaikambo
2004-08-30 20:04       ` Dominik Brodowski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-09 19:54 Dominik Brodowski
2004-08-14 20:47 ` Zwane Mwaikambo

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=20040830200438.GC8563@dominikbrodowski.de \
    --to=linux@dominikbrodowski.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@redhat.com \
    --cc=zwane@linuxpower.ca \
    /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