From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <542A1A21.4070406@kernel.dk> Date: Mon, 29 Sep 2014 20:49:05 -0600 From: Jens Axboe MIME-Version: 1.0 Subject: Re: Limit LBA Range References: <5429B424.7080903@kernel.dk> <5429C839.7090408@kernel.dk> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit To: Sitsofe Wheeler , Jon Tango Cc: "fio@vger.kernel.org" List-ID: On 2014-09-29 20:23, Sitsofe Wheeler wrote: > On 29 September 2014 22:10, Jon Tango wrote: >> >> I include both of those commands, in addition to size=745g, and it seems to >> be conducting the workload over the entire LBA range. Is this the correct >> combination of the three parameters? Here is the test script: >> >> [global] >> name=4ktest >> filename=\\.\physicaldrive1 >> direct=1 >> numjobs=8 >> norandommap >> ba=4k >> time_based >> size=745g >> log_avg_msec=100000 >> group_reporting=1 >> ######################################################### >> >> [4K Precon] >> stonewall >> runtime=15000 >> iodepth=32 >> bs=4k >> rw=randwrite > > Bear in mind that because you are asking for eight stonewalled jobs > this fio run will take 8 * 15000 seconds (around 33 hours) to finish > because after the first job has run for four hours the second job will > start etc. Since they are grouped with numjobs=x, they belong to the same group. Hence the stonewall isn't going to do anything here. If it was split in two precondition sections, ala: [global] numjobs=4 ... [4K Precon stage 1] runtime=15000 iodepth=32 bs=4k rw=randwrite [4K Precon stage 2] stonewall runtime=15000 iodepth=32 bs=4k rw=randwrite Then stage 2 would not start until stage 1 had finished. -- Jens Axboe