From: Borislav Petkov <bp@alien8.de>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
x86@kernel.org, Linux Torvalds <torvalds@osdl.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCHv2] x86: add kconfig options for newer 64-bit processors
Date: Mon, 21 Oct 2013 12:54:01 +0200 [thread overview]
Message-ID: <20131021105401.GA5019@nazgul.tnic> (raw)
In-Reply-To: <52646E0E.6040204@gmail.com>
On Sun, Oct 20, 2013 at 07:58:06PM -0400, Austin S Hemmelgarn wrote:
> I am not trying to say that this provides any improvement in speed (or
> at least the AMD options, the one for Intel Ivy Bridge processors does
> appear to do better in this respect).
"Does appear" is not a very good answer - you need to give concrete
benchmark results which people can repeat on their own and confirm your
observations.
> As I stated in the comments just before the patch itself, "...testing
> of MPILEDRIVER seems to indicate an improvement to energy efficiency
> over GENERIC_CPU as it causes the on cpu power sensor to consistently
> read an average of 1.5 watts lower under idle load than when
> using GENERIC_CPU (this corresponds to about 5% decrease in power
> consumption on a idle-tickless system, and about 2% on a non-dynticks
> system.).". While this result is dependent on a large number of
> factors (not the least of which being that I have my CPU over-clocked
> to the point that the lowest C-state runs at 1.4GHz, which really
> hurts energy efficiency) it is still a positive result, and most of
> the equivalent options primarily improve energy efficiency.
Again, how exactly do I reproduce your observations on my boxes? I need
a step-by-step walk through please.
> Also, you have to understand that my target audience isn't the
> mainstream distros,...
Well, if your target audience is only a very small fraction of the linux
users, then we don't need this in the mainline kernel in the first
place, do we?
Thanks.
next prev parent reply other threads:[~2013-10-21 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 0:37 Austin S Hemmelgarn
2013-10-20 8:17 ` Richard Weinberger
2013-10-20 9:18 ` Borislav Petkov
2013-10-20 23:58 ` Austin S Hemmelgarn
2013-10-21 10:54 ` Borislav Petkov [this message]
2013-10-21 11:44 ` Austin S Hemmelgarn
2013-10-21 13:59 ` Borislav Petkov
2013-10-21 14:20 ` Austin S Hemmelgarn
2013-10-22 8:23 ` Borislav Petkov
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=20131021105401.GA5019@nazgul.tnic \
--to=bp@alien8.de \
--cc=ahferroin7@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.org \
--cc=x86@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
all inboxes | Powered by JetHome®