From mboxrd@z Thu Jan  1 00:00:00 1970
From: Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH v3 1/3] cpufreq: ondemand: Change the calculation of
 target frequency
Date: Sun, 9 Jun 2013 23:14:49 +0200
Message-ID: <20130609211449.GA5517@pd.tnic>
References: <q46r5iepl3sunqe5eemv66hk.1370694869222@email.android.com>
 <20130609162653.GA5004@pd.tnic>
 <51B4C497.2030308@semaphore.gr>
 <7661669.NhG4BEI8zO@vostro.rjw.lan>
Mime-Version: 1.0
Return-path: <cpufreq-owner@vger.kernel.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alien8.de; s=alien8;
	t=1370812491; bh=NP7PvqunO4ZVJ1Tz7Zm5oFZgtBUfkWhW8sViYNsfUzw=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:In-Reply-To; b=HfBYhtY+vHY5ZXN6SV0i7hWyWoNaIGIKhw/UvO
	W5KVEAnocosvqsJhjA4SubEbLgIxM1s0L8vG4LcanwIPvnhRvMFPrZ8HKeQ93rsxfOv
	jjYHGF8qStOzMXgXfdR9KmwW9/IDRKxwqsHF0YTIGSJcaNXyibdTJjVcLJctWu5R0A=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alien8.de; s=alien8;
	t=1370812490; bh=NP7PvqunO4ZVJ1Tz7Zm5oFZgtBUfkWhW8sViYNsfUzw=;
	h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:
	 Content-Type:In-Reply-To; b=IuMsDAKmkR/cBsG8zHoMmjLuvdN7sclC+Z/7+2
	ppe5qspzZmmaawbCifKa5rHLy/epx+IYVcC0EyEqQ6eZhlaLWnfEBO204eeUFPYZV6d
	yHKjqg8kbsDQV8tjbJ8BFqPQeI3jpXxjwJc8VFKAnXc5tMIRU0xjdMqzl9hGnFigL8=
Content-Disposition: inline
In-Reply-To: <7661669.NhG4BEI8zO@vostro.rjw.lan>
Sender: cpufreq-owner@vger.kernel.org
List-ID: <cpufreq.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Stratos Karafotis <stratosk@semaphore.gr>, Borislav Petkov <bp@suse.de>, Viresh Kumar <viresh.kumar@linaro.org>, Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>, linux-pm@vger.kernel.org, cpufreq@vger.kernel.org, linux-kernel@vger.kernel.org

On Sun, Jun 09, 2013 at 10:58:51PM +0200, Rafael J. Wysocki wrote:
> Can you possibly prepare a graph showing both the execution time
> and energy consumption for several different loop durations in your
> program (let's keep the 5000 us sleep for now), including multiples of
> sampling_rate as well as some other durations?

Judgind by the times in C0 one of the cores spent, this small program
is single-threaded and is a microbenchmark. And you know how optimizing
against a microbenchmark doesn't really make a lot of sense.

I wonder if lmbench or aim9 or whatever would make more sense to try
here...

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--