[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131218102412.GC20360@gmail.com>
Date: Wed, 18 Dec 2013 11:24:12 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Mel Gorman <mgorman@...e.de>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Alex Shi <alex.shi@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Fengguang Wu <fengguang.wu@...el.com>,
H Peter Anvin <hpa@...or.com>, Linux-X86 <x86@...nel.org>,
Linux-MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH 0/4] Fix ebizzy performance regression due to X86 TLB
range flush v2
* Mel Gorman <mgorman@...e.de> wrote:
> > Thanks again for going through all this. Tracking multi-commit
> > performance regressions across 1.5 years worth of commits is
> > generally very hard. Does your testing effort comes from
> > enterprise Linux QA testing, or did you ran into this problem
> > accidentally?
>
> It does not come from enterprise Linux QA testing but it's motivated
> by it. I want to catch as many "obvious" performance bugs before
> they do as it saves time and stress in the long run. To assist that,
> I setup continual performance regression testing and ebizzy was
> included in the first report I opened. [...]
Neat!
> [...] It makes me worry what the rest of the reports contain.
It will be full with reports of phenomenal speedups!
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists