From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <542AC26A.7030608@kernel.dk> Date: Tue, 30 Sep 2014 08:47:06 -0600 From: Jens Axboe MIME-Version: 1.0 Subject: Re: Limit LBA Range References: <5429B424.7080903@kernel.dk> <5429C839.7090408@kernel.dk> <542A1A21.4070406@kernel.dk> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit To: Andrey Kuzmin , Jon Tango Cc: Sitsofe Wheeler , fio@vger.kernel.org List-ID: On 2014-09-30 02:57, Andrey Kuzmin wrote: > The same thing could be done by partitioning the SSD in the operating > system with the desired partition size, and then running a time-based > fio job against the partition. > > Basically, fio options offset/size should yield the same net result, > but I'm always unsure on what is the actual effect of mixing size and > time_based in a single job, and whether fio will wrap around the > specified size to the specified offset if the job is time-based. HOWTO > could have used some clarification on size/time_based interaction. The HOWTO currently states: time_based If set, fio will run for the duration of the runtime specified even if the file(s) are completely read or written. It will simply loop over the same workload as many times as the runtime allows. Especially the last sentence should make it clear, that it will simply run the specified workload over and over until the time has passed. I'd welcome changes to make that clearer, if it doesn't get the point across. -- Jens Axboe