From: Fengguang Wu <fengguang.wu@intel.com>
To: Christoph Lameter <cl@linux.com>
Cc: Daniel Borkmann <dborkman@redhat.com>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] Application performance: regressions, controlling preemption
Date: Fri, 15 Aug 2014 12:13:12 +0800 [thread overview]
Message-ID: <20140815041312.GB15844@localhost> (raw)
In-Reply-To: <alpine.DEB.2.11.1408141216180.26922@gentwo.org>
On Thu, Aug 14, 2014 at 12:17:38PM -0500, Christoph Lameter wrote:
> On Thu, 14 Aug 2014, Fengguang Wu wrote:
>
> > The proc-vmstat, perf-profile, cpuidle, turbostat etc. "monitors" are
> > inspired by Mel Gorman's mmtests suite and they are really helpful in
> > catching&analyzing the subtle impacts a patch might bring to the system.
>
> Mel also has some interesting tests in the suite like the page fault test
> and aim9 among numerous others. Could those also be added?
Sure. I just added aim9 to the TODO list.
pft is already included in lkp-tests:
% ls */pft
jobs/pft.yaml pack/pft pack/pft.patch stats/pft tests/pft
Thanks,
Fengguang
next prev parent reply other threads:[~2014-08-15 4:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 14:32 [Ksummit-discuss] [TOPIC] Application performance: regressions, controlling preemption Chris Mason
2014-05-12 15:05 ` Davidlohr Bueso
2014-05-12 15:57 ` Jan Kara
2014-05-12 16:18 ` Andy Lutomirski
2014-05-12 23:16 ` Greg KH
2014-05-13 1:43 ` Chris Mason
2014-05-14 1:31 ` Li Zefan
2014-05-14 12:27 ` Chris Mason
2014-05-13 12:27 ` Jan Kara
2014-05-12 23:54 ` Josh Triplett
2014-05-13 0:31 ` Davidlohr Bueso
2014-08-14 15:01 ` Fengguang Wu
2014-08-14 17:17 ` Christoph Lameter
2014-08-15 4:13 ` Fengguang Wu [this message]
2014-08-15 14:07 ` Christoph Lameter
2014-08-16 1:32 ` [Ksummit-discuss] 0day kernel performance/power test service Fengguang Wu
2014-05-28 17:08 ` [Ksummit-discuss] [TOPIC] Application performance: regressions, controlling preemption Paul E. McKenney
2014-08-18 6:21 ` Fengguang Wu
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=20140815041312.GB15844@localhost \
--to=fengguang.wu@intel.com \
--cc=cl@linux.com \
--cc=dborkman@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.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.