All of lore.kernel.org
 help / color / mirror / Atom feed
From: "majun (F)" <majun258@huawei.com>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Help: FIO testing problem on arm64
Date: Thu, 29 Jan 2015 09:36:26 +0800	[thread overview]
Message-ID: <54C98E9A.5010500@huawei.com> (raw)

Hi All:
	I met a problem while testing the ramdisk peformance using fio.
	The platform is arm64 , fio version is 2.1.10.
	
	The ramdisk is enabled on my platform , so there are dev/ram0 ...to dev/ram15 totall 16 ramdisk devices.
	I tried to test these ramdisks performance uisng the script file list as below.

#!/bin/bash

#disk_list=`lsscsi | awk '{print $NF}' | cut -d/ -f3`
disk_list="ram1 ram2 ram3 ram4 ram5 ram6 ram7 ram8 ram9 ram10 ram11 ram12 ram13 ram14 ram15"
numjobs=1
runtime=180
	
run_18disk_test()
{
logdir=/root/18disk_performance_test
rm -rf $logdir
mkdir $logdir
for rw in read write randread randwrite
	do
		for bs in 4K 1M
		do
			for iodepth in 1 2 4 8 16 32
			do
				for disk in `echo $disk_list`
				do
					iodepth_2=`printf "%02d" $iodepth`
					fio --time_based --filename=/dev/$disk --rw=$rw --bs=$bs --ioengine=libaio --direct=1 --numjobs=$numjobs --iodepth=$iodepth --name=test --group_reporting --runtime=$runtime &> $logdir/${disk}_${bs}_${rw}_numjobs${numjobs}_iodepth${iodepth_2}.log &
				done
				sleep $runtime
			done
		done
done
}

	

	But the test result is not ok.
	The error log is:

test: (g=0): rw=write, bs=4K-4K/4K-4K/4K-4K, ioengine=libaio, iodepth=1
fio-2.1.14
Starting 1 process
fio: cache invalidation of /dev/ram2 failed: Device or resource busy
fio: cache invalidation of /dev/ram2 failed: Device or resource busy
fio: cache invalidation of /dev/ram2 failed: Device or resource busy
fio: cache invalidation of /dev/ram2 failed: Device or resource busy
fio: cache invalidation of /dev/ram2 failed: Device or resource busy
fio: cache invalidation of /dev/ram2 failed: Device or resource busy
fio: cache invalidation of /dev/ram2 failed: Device or resource busy
fio: cache invalidation of /dev/ram2 failed: Device or resource busy

	



             reply	other threads:[~2015-01-29  1:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29  1:36 majun (F) [this message]
2015-01-30  8:48 ` Help: FIO testing problem on arm64 Philip Keogh
2015-02-02  0:51   ` majun (F)
2015-01-31  1:25 ` Kulkarni, Vasu

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=54C98E9A.5010500@huawei.com \
    --to=majun258@huawei.com \
    --cc=fio@vger.kernel.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.