mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Heidelberger <david.heidelberger@ixit.cz>
To: John <da_audiophile@yahoo.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] expand micro-optimizations in kernel to newer model CPUs
Date: Tue, 10 Dec 2013 04:51:41 +0100	[thread overview]
Message-ID: <864985fbeb1d8148439e25ec01f47a67@ixit.cz> (raw)
In-Reply-To: <1386518000.90452.YahooMailNeo@web140004.mail.bf1.yahoo.com>

Hello,

this patch is used in Gentoo geek-sources and mptcp-sources (and 
probably in lot other kernel sources sets). So, there was lot testing.

It's not _big_ performance difference, but -mtune=native is nice to 
have.
It could be great, if this kernel option could be fully utilized without 
need of additional patching.

Thank for your work guys.

Cheers,
David

Dne 2013-12-08 16:53, John napsal:
> I have been maintaining the attached patch since kernel v3.9.[1]  I
> submit for review the most recent incarnation which works with the
> v3.12 tree.  As you can see by the ANOVA plots referenced in the
> comments, these micro optimizations are value-added statistically
> based on a compilation endpoint and are on-par with the included
> "core2" option in the mainline kernel itself.
> 
> I maintain an unofficial Arch Linux kernel repo and have been
> building/packaging kernels using this patch for many different CPUs
> and Arches.  I feel this code has been tested by the >2,500 users of
> my repo on many different CPUs and under both x86 and x86_64
> systems[2] and feel it is worth for inclusion into the mainline
> kernel.
> 
> Please cc me on replies as I am NOT a regular subscriber to lkml. 
>  Thank you.
> 
> 1. https://github.com/graysky2/kernel_gcc_patch
> 2, http://repo-ck.com/stats.pdf

  reply	other threads:[~2013-12-10  3:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-08 15:53 John
2013-12-10  3:51 ` David Heidelberger [this message]
2013-12-13 12:37   ` Austin S Hemmelgarn
     [not found]     ` <1387051250.86178.YahooMailNeo@web140005.mail.bf1.yahoo.com>
     [not found]       ` <ce679ca5-bf83-4c2a-9234-859cc7a4206b@email.android.com>
     [not found]         ` <1387057337.97000.YahooMailNeo@web140004.mail.bf1.yahoo.com>
     [not found]           ` <52ACECC4.208@zytor.com>
2013-12-15 12:00             ` John
2013-12-15 12:27               ` Richard Weinberger
2013-12-15 12:42                 ` John
2013-12-15 13:23                   ` Borislav Petkov
2013-12-15 17:31                   ` Richard Weinberger
2013-12-16 14:28               ` Ingo Molnar
2013-12-17 12:59                 ` Austin S Hemmelgarn
2013-12-15 12:23     ` John

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=864985fbeb1d8148439e25ec01f47a67@ixit.cz \
    --to=david.heidelberger@ixit.cz \
    --cc=da_audiophile@yahoo.com \
    --cc=linux-kernel@vger.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

Powered by JetHome