All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] dio: reduce the number of cycles
Date: Wed, 14 Jun 2017 11:38:30 +0800	[thread overview]
Message-ID: <20170614033830.12736-1-liwang@redhat.com> (raw)

These two cases (dio29/30) takes a bit long time in dio test, but they're not stress
test, so I suggest reducing the number of cycles.

On my RHEL-7.3 (23G RAM, 24 CPU(s), x86_64) box, it takes almost 9 mins.

  diotest06    1  TPASS  :  Read with Direct IO, Write without
  diotest06    2  TPASS  :  Write with Direct IO, Read without
  diotest06    3  TPASS  :  Read, Write with Direct IO
  diotest06    0  TINFO  :  3 testblocks 1000 iterations with 100 children completed

  real	8m4.805s
  user	71m36.722s
  sys	8m51.649s

Signed-off-by: Li Wang <liwang@redhat.com>
---
 runtest/dio | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/runtest/dio b/runtest/dio
index a26e001..185cd57 100644
--- a/runtest/dio
+++ b/runtest/dio
@@ -40,8 +40,8 @@ dio27 diotest6 -b 8192 -o 1024000 -i 1000 -v 100
 dio28 diotest6 -b 8192 -o 1024000 -i 1000 -v 200
 
 ### Run the tests with more children
-dio29 diotest3 -b 65536 -n 100 -i 1000 -o 1024000
-dio30 diotest6 -b 65536 -n 100 -i 1000 -o 1024000
+dio29 diotest3 -b 65536 -n 100 -i 100 -o 1024000
+dio30 diotest6 -b 65536 -n 100 -i 100 -o 1024000
 #
 # RAW DEVICE TEST SECTION
 #   DEV1 and DEV2 should be exported prior to execution or
-- 
2.9.3


             reply	other threads:[~2017-06-14  3:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14  3:38 Li Wang [this message]
2017-06-14 11:16 ` [LTP] [PATCH] dio: reduce the number of cycles Eryu Guan
2017-06-14 13:49   ` Cyril Hrubis
2017-06-15  6:54     ` Eryu Guan
2017-06-15  9:23       ` Cyril Hrubis
2017-06-15  9:38         ` Li Wang
2017-06-15 13:17           ` Cyril Hrubis

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=20170614033830.12736-1-liwang@redhat.com \
    --to=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    /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.