All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
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 23:30:26 +0200	[thread overview]
Message-ID: <20130929213026.GF5426@pd.tnic> (raw)
In-Reply-To: <52489A59.7040108@gmail.com>

On Sun, Sep 29, 2013 at 05:23:37PM -0400, Austin S Hemmelgarn wrote:
> 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.

If it doesn't bring any performance improvement - and I don't want to
rain on your parade but I think it won't, at least not enough to warrant
a serious look - there's absolutely no reason to add it.

But hey, I'm always open to surprises! So surprise me!

:-)

-- 
Regards/Gruss,
    Boris.

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

  reply	other threads:[~2013-09-29 21:30 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
2013-09-29 21:30         ` Borislav Petkov [this message]
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=20130929213026.GF5426@pd.tnic \
    --to=bp@alien8.de \
    --cc=ahferroin7@gmail.com \
    --cc=alan@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.