From: Dor Laor <dlaor@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: lmr@redhat.com, Mark McLoughlin <markmc@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Michael Goldish <mgoldish@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] Re: Networking patches queue
Date: Sun, 31 May 2009 23:58:48 +0300 [thread overview]
Message-ID: <4A22EF88.6090404@redhat.com> (raw)
In-Reply-To: <4A1EB442.1060006@us.ibm.com>
Anthony Liguori wrote:
..
> Does kvm-autotest have networking tests?
>
>
Yes and no...
kvm autotest is able to run standard autotest tests -
http://www.linux-kvm.org/page/KVM-Autotest/Tests#autotest
autotest itself support various tests, netperf2 is one of them. So with
a little effort it is doable.
We'll try to make it easy as possible to run these tests.
Here's a list of some autotest tests:
aborttest dacapo error_test_na iperf
lsb_dtk profiler_test stress
aio_dio_bugs dbench fio ipv6connect
ltp reaim sysbench
aiostress dbt2 fsdev isic
memory_api real_time_tests tbench
barriertest disktest fsfuzzer kernbench
monotonic_time rmaptest tiobench
bash_shared_mapping error_cleanup fs_mark kernelbuild
netperf2 rttester tsc
bonnie error_initialize fsstress kvm_runtest_2
netpipe scrashme unixbench
btreplay error_setup fsx kvm_runtest_old
parallel_dd selftest uptime
compilebench error_skip_step hackbench kvmtest
perfmon signaltest xmtest
cpu_hotplug error_test_bug interbench libhugetlbfs
pi_tests sleeptest
cpuset_tasks error_test_error iosched_bugs linus_stress
pktgen sparse
cyclictest error_test_fail iozone lmbench
posixtest spew
> I know there's some concern about the time it takes for patches to get
> applied. IMHO, the best way to improve that it to get a stronger set of
> functional tests. I have a set I've been working on but it's on my
> other laptop which I cannot reach ATM :-/
>
> As has been discussed before, I'm looking for finer grain functional
> tests than the installation tests that kvm-autotest is providing now.
> I'm not saying that this series requires submitting a test suite first,
> but rather that if you're interested in seeing networking advance more
> rapidly, a good investment would be to build out a better test
> infrastructure for it.
>
> Regards,
>
> Anthony Liguori
>
>
>
next prev parent reply other threads:[~2009-05-31 20:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 15:19 [Qemu-devel] Networking patches queue Mark McLoughlin
2009-05-28 15:28 ` [Qemu-devel] " Anthony Liguori
2009-05-28 15:51 ` Jan Kiszka
2009-05-28 16:57 ` Mark McLoughlin
2009-05-28 20:26 ` Anthony Liguori
2009-05-28 17:01 ` Glauber Costa
2009-05-28 17:19 ` Jan Kiszka
2009-05-28 19:10 ` Jan Kiszka
2009-05-28 15:51 ` Mark McLoughlin
2009-05-28 15:56 ` Anthony Liguori
2009-05-28 16:52 ` Mark McLoughlin
2009-05-31 20:58 ` Dor Laor [this message]
2009-06-09 21:43 ` Mark McLoughlin
2009-06-10 23:08 ` Anthony Liguori
2009-06-11 1:27 ` Anthony Liguori
2009-06-11 8:34 ` Mark McLoughlin
2009-06-11 8:38 ` Gerd Hoffmann
2009-06-11 9:42 ` [Qemu-devel] [PATCH] Fix xilinx_ethlite breakage by 4f1c942b7f Jan Kiszka
2009-06-11 10:48 ` [Qemu-devel] " Mark McLoughlin
2009-06-11 11:48 ` [Qemu-devel] Re: Networking patches queue Paul Brook
2009-06-11 12:50 ` Anthony Liguori
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=4A22EF88.6090404@redhat.com \
--to=dlaor@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=lmr@redhat.com \
--cc=markmc@redhat.com \
--cc=mgoldish@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).