From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
Linux Torvalds <torvalds@osdl.org>, Alan Cox <alan@redhat.com>
Subject: Re: [PATCH 1/1] x86_64: add config options to optimize for newer AMD processors
Date: Sun, 29 Sep 2013 17:23:37 -0400 [thread overview]
Message-ID: <52489A59.7040108@gmail.com> (raw)
In-Reply-To: <20130929205051.GD5426@pd.tnic>
On 09/29/2013 04:50 PM, Borislav Petkov wrote:
> On Sun, Sep 29, 2013 at 04:41:02PM -0400, Austin S Hemmelgarn
> wrote:
>> While I understand that you want decisive proof that it provides
>> an improvement, does it specifically matter if the option is
>> unused by most people and doesn't result in a negative
>> performance hit when used?
>
> Just having the option for no good reason at all is a no-no.
I'm not saying that should just be included without substantiation, I
simply mean that the reason to include it (as far as I am concerned)
is that it doesn't break anything and provides something useful that
isn't in the kernel already.
Despite this I am still happy to benchmark it to provide some more
concrete proof.
next prev parent reply other threads:[~2013-09-29 21:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 17:54 [PATCH 1/1] x86_64: add config options to optimize for newer AMD processors Austin S Hemmelgarn
2013-09-29 18:01 ` Borislav Petkov
2013-09-29 20:41 ` Austin S Hemmelgarn
2013-09-29 20:50 ` Borislav Petkov
2013-09-29 21:23 ` Austin S Hemmelgarn [this message]
2013-09-29 21:30 ` Borislav Petkov
2013-10-03 13:42 ` Austin S Hemmelgarn
[not found] ` <524D5DAC.3000004@gmail.com>
2013-10-03 16:27 ` Linus Torvalds
2013-10-03 16:57 ` Borislav Petkov
2013-10-03 18:12 ` Austin S Hemmelgarn
2013-10-03 18:28 ` 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=52489A59.7040108@gmail.com \
--to=ahferroin7@gmail.com \
--cc=alan@redhat.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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