All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Chris Mason <clm@fb.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] Application performance: regressions, controlling preemption
Date: Mon, 18 Aug 2014 14:21:01 +0800	[thread overview]
Message-ID: <20140818062101.GA12707@localhost> (raw)
In-Reply-To: <5370DB7B.2040706@fb.com>

Hi Chris,

> The KS dates should put us right at the end of our regression hunt, I can
> talk through the main problems we hit, how (if) we fixed them and hopefully
> offer tests to keep them from coming back.

It'd be sweet if your tests (and others') can be added to

        git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests

Which runs in Intel actively to keep the relevant regressions from
coming back.

Currently the repository has test cases

wfg /c/lkp-tests% ls tests
aim7       debug-test  fio-jbod  glbenchmark  kbuild            nepim    packetdrill            piglit  sockperf  tlbflush        wrapper
blogbench  ebizzy      fsmark    hackbench    kernel_selftests  netperf  perf-bench-numa-mem    pigz    tbench    unixbench       xfstests
dbench     fileio      ftq       iozone       linpack           nuttcp   perf-bench-sched-pipe  qperf   tcrypt    vm-scalability
dd         fio         fwq       iperf        ltp               oltp     pft                    sleep   thrulay   will-it-scale

Which is not only too few in number, but also rather limited in test
parameters and system setups. For example, if run them in different
cgroup/numa/governor/network/... setups, or even with different
kernel configs, the results may become quite different.

Thanks,
Fengguang

      parent reply	other threads:[~2014-08-18  6:21 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
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 [this message]

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=20140818062101.GA12707@localhost \
    --to=fengguang.wu@intel.com \
    --cc=clm@fb.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.